Hello all I’m very excited to be part of the Let’s Encrypt beta. It’s a great service so I’d like to start by saying, “Thanks!” That said… I’ve found the DV process to be rather inconvenient (especially when compared to sslmate.com ’s process). The biggest problem is the client’s need for ports …

Or use a webserver like ngnix in front of you webapp. Let nginx serve static contents (including .well-known/acme-chalenge) and forwarding request for dynamic content to you webapp. It is a pretty common setup…

adding a dependency(nginx) just so that let’s encrypt can validate on port 80 and 443 is not a solution it’s a patch and adds complexity to systems that don’t need it

If your infrastructure is so crippled you can't even host on port 80, maybe even more band-aids and kludges isn't the solution. IMO, the "kludge" is requiring permanent changes to nginx or apache configuration just to support a single HTTP request once every 90 days. In my case, my web server ha…

[image] mehaase: My rewrite rules redirect all requests on port 80 to port 443 with an HSTS pin, so I also need to modify the rewrite rules to exclude the .well-known directory. That's not necessary. The CA server will follow redirects (even to https://) and will happily ignore HSTS. As long …

Yep! The initial request is HTTP anyway, so there’s no reason to be concerned about MitM for the follow-up connection. The CA server will happily accept self-signed or expired certificates for http-01.

+1 to add the option to use a challenge in a port other than 80 and 443. IMO this would be the ideal solution for servers that are not serving static content whatsoever: run the standalone server in a different port, not interfering with either http or https traffic. A parametrized port for the ch…

Joined to say +1 for allowing clients to use privileged ports other than 80 and 443 to complete the domain validation using HTTP. I do not understand why allowing the validation to take place using, say, port 444 results in a less trustworthy certificate than a validation using port 443. As a syste…

[image] cmart: I do not understand why allowing the validation to take place using, say, port 444 results in a less trustworthy certificate than a validation using port 443. Port 444 is not typically a port that serves websites. It is conceivable, for example, that your network security team …

Support for ports other than 80 and 443

Feature Requests

mehaase May 3, 2016, 4:52pm 68

Will it ignore the invalid certificate that I have running on port 443?

Topic		Replies	Views
Domain validation on 80 and 443 but no override? Server	13	5030	October 25, 2016
HTTP-01 and AWS challenge Feature Requests	18	346	May 30, 2026
Http challange on port 25? Feature Requests	25	2486	February 13, 2023
Any way I can get certificates for my scenario? Issuance Tech	6	2332	June 10, 2016
Acme challenges over HTTPS Feature Requests	37	13741	March 11, 2022

Support for ports other than 80 and 443

Related topics