-
Notifications
You must be signed in to change notification settings - Fork 174
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
Drop port 80 requirement #137
Comments
The requirement is only really there's for caddy to get the tls cert, afaik. If you do your certs through letsencrypt any other way, like through traefik, and use that to do your reverse proxy, you should be able to drop the port 80 entirely. I did, anyway. |
That's good to know, perhaps the issue can be resolved with documentation. |
I'm fairly certain that Let's Encrypt requires port 80 to get an initial certificate (with Caddy, traefik, or anything else), though I don't think port 80 is required for renewals. If you're using DNS with let's encrypt then you don't need any ports open (as far as getting certs is concerned). |
LetsEncrypt supports tls-alpn-01, which does not require port 80. Caddy supports it, so does traefik |
Then it would be great for the project to switch to tls-alpn-01 and drop the port 80 requirement. |
I only expose port 443 for my website and likewise only want to expose port 443 for PDS. If browsers don't need port 80, can PDS also drop the port 80 requirement?
The text was updated successfully, but these errors were encountered: