Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IP2TOR+LestEncrypt: Check if working #1412

Closed
rootzoll opened this issue Aug 5, 2020 · 2 comments
Closed

IP2TOR+LestEncrypt: Check if working #1412

rootzoll opened this issue Aug 5, 2020 · 2 comments
Milestone

Comments

@rootzoll
Copy link
Collaborator

rootzoll commented Aug 5, 2020

It looks like that sometimes it takes some time until duckdns is updated on a new IP (I mean when the local DNS resolution with TTL catches on to a change). So there should be a warning on services that use LetsEncrypt - that its waiting on updating DNS.

In general a better "Test" if everything is running (HTTPS delivering 'a page', etc) would be great.

@rootzoll rootzoll added this to the 1.6.1 Release milestone Aug 5, 2020
@rootzoll rootzoll changed the title Check DuckDNS delivering correct IP IP2TOR+LestEncrypt: Check if working Sep 14, 2020
@rootzoll
Copy link
Collaborator Author

Now integrated to checks into blitz.subscriptions.letsencrypt.py:

  • domain resolves to the wanted IP
  • https gives a 200 response on a testport given

The menu elements of LNbits and BTCPayServer check now on this when called and show warning if one of the tests fail.

rootzoll pushed a commit that referenced this issue Sep 14, 2020
@rootzoll rootzoll added the final testing was fixed - needs testing label Sep 14, 2020
@rootzoll
Copy link
Collaborator Author

Tests looking good. Closing for v1.6.1 release.

@rootzoll rootzoll removed the final testing was fixed - needs testing label Oct 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant