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 …

[image] My1: use webroot or manual then you just put a file in your web root ( the folder that is the main folder of your internet domain) and you are good to go. that's exact what i use webroot authentication for - I've fully automated the Letsencrypt webroot process including auto renewal f…

well if I could get my raspi to get the correct webrrot for each of my domains and push the files to my win PC fine, but if I can get it running through a different port that can be forwarded to my raspi in one step I’ll gladly do that

I’m in the same situation of @sdc395 : being forced to close all applications that use the 80 and 443 ports is really annoying (in my case nginx and OpenVPN). Also, I prefer not to use the webroot method because I have a lot of subdomains to authenticate and some of them are not even used in nginx,…

[image] Rahff: Also, I prefer not to use the webroot method because I have a lot of subdomains to authenticate and some of them are not even used in nginx, but for a mail server. if you use nginx you can also setup a default server to handle LE SAN SSL multi-domains outlined at Using the webr…

There are also other SSL Servers that can solve the ServerNameInformation challenge: SMTP(S) IMAP(S) POP3(S) Realy cool would it then the boulder server would support these protocols including STARTTLS but i think this is an feature that will be on the long term list.

@sdc395 did you see that you can specify port? [image] LE client needs to bind to port 80, which I'm already using Help I…

Yes, thank you, but this isn’t really a solution. I still have to “integrate” the LE client with my web server config (the proxy settings). I’ve settled for the webroot approach for now but I’m still keen on the idea of the LE client being truly standalone and playing nicely with other services.

I haven’t seen anyone mention this issue yet, which is, what if my server is running from a residential address where the ISP blocks port 443 and 80. This is the case for me.

You can use the standalone method and specify the particular port you wish to validate over. You might also be able to use the webroot method, but I’m not sure if you can specify the port on that. Someone more familiar with the reference client may know.

Support for ports other than 80 and 443

Feature Requests

pierreozoux November 17, 2015, 8:57am 19

@sdc395 did you see that you can specify port?

Topic		Replies	Views
Domain validation on 80 and 443 but no override? Server	14	5012	November 24, 2016
Http challange on port 25? Feature Requests	26	2439	March 15, 2023
Any way I can get certificates for my scenario? Issuance Tech	7	2316	July 10, 2016
Acme challenges over HTTPS Feature Requests	38	13505	April 10, 2022
Alternative for allowing letsencrypt file auth connections for a geo-restricted server Feature Requests	41	421	December 17, 2024

Support for ports other than 80 and 443

Related topics