ACME and non-standard webgui port

[eshield]

Hello,

Long time ago I've noticed an unpleasant issue where one can not validate cert using very splendid "webroot local folder" method when an unusual port is used for WebGUI … like 43265. I have some nasty pfSense boxes with non-standard port configured and all of them can't be validated using method above because "validationRecord" object contains key "Port" with value of "80" which is totally wrong. I believe there should be a checkbox like "Use current WebGUI port" or any other way to deal with it. I hope this is not against any funny laws?

Thanks.

P.S: My ISP blocks incoming 80 and 443 ports.

[Gertjan]

The acme package uses "acme" that adheres to the 'acme' protocol : see here what the answer was June 2017 :

https://community.letsencrypt.org/t/how-to-get-a-certificate-without-using-port-80/36192/8

Entire forum thread : How to get a certificate, without using port 80? (or any other port)

[jimp]

You will have to use a DNS-based validation method. ACME requires port 80. TLS validation on port 443 is also no longer supported.