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

Nextcloud: Caddy can fail to get TLS certificate with public IPv4 #232

Open
scottyeager opened this issue May 2, 2024 · 0 comments · May be fixed by #233
Open

Nextcloud: Caddy can fail to get TLS certificate with public IPv4 #232

scottyeager opened this issue May 2, 2024 · 0 comments · May be fixed by #233

Comments

@scottyeager
Copy link
Contributor

User reported a TLS error when trying to connect to their NextCloud instance with a public IP and custom domain. Upon inspection, I found that Caddy was failing to get a TLS certificate because DNS was not yet propagated when Caddy started and Caddy performs limited retries on each start.

The solution would be to wait for DNS propagation to complete before starting Caddy.
@scottyeager scottyeager linked a pull request May 2, 2024 that will close this issue
Open
@xmonader xmonader modified the milestone: 3.15.x Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

NextCloud, wait for dns propagation with public IPv4 threefoldtech/tf-images
2 participants
@xmonader @scottyeager