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.

Sign up for GitHub

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

Jump to bottom

Recheck DuckDNS #4547

Open
rootzoll opened this issue Apr 18, 2024 · 3 comments · May be fixed by #4560
Open

Recheck DuckDNS #4547

rootzoll opened this issue Apr 18, 2024 · 3 comments · May be fixed by #4560
Labels
final testing was fixed - needs testing
Milestone
1.11.1 Release

Comments

@rootzoll
Copy link
Collaborator

duckdns
@rootzoll rootzoll added the bug - unconfirmed Something isn't working - not (yet) reproduced label Apr 18, 2024
@rootzoll rootzoll added this to the 1.11.1 Release milestone Apr 18, 2024
@cdemkos
Copy link

cdemkos commented Apr 18, 2024

Bildschirmfoto vom 2024-04-18 22-16-23

@rootzoll
Copy link
Collaborator Author

Also recheck #2255 when on this

This was referenced May 1, 2024
Closed
Open
@rootzoll
Copy link
Collaborator Author

rootzoll commented May 1, 2024

Seems like an email is now required to run letsencrypt on duckdns ... PR #4560 should fix this with v1.11.1rc1

@rootzoll rootzoll added final testing was fixed - needs testing and removed bug - unconfirmed Something isn't working - not (yet) reproduced labels May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
final testing was fixed - needs testing
Projects
None yet
Milestone
1.11.1 Release
Development

Successfully merging a pull request may close this issue.

Update acme.sh & fix duckdns raspiblitz/raspiblitz
2 participants
@rootzoll @cdemkos