Certbot validation on non standard port

[jjrushford]

I run a WebDAV server using TLS and authentication using a self signed certificate. The WebDAV server is exposed on a non-standard port. I'd like to get a Let's Encrypt certificate and would use the certbot tool on my server so that I may be validated as the owner.

My question, does Let's Encrypt support certbot validation on ports other than 443?

thanks
John

[Bruce5051]

Hello @jjrushford, welcome to the Let's Encrypt community.

This is a Let’s Encrypt, not really Certbot, requirement for HTTP-01 challenge states "The HTTP-01 challenge can only be done on port 80." and "Our implementation of the HTTP-01 challenge follows redirects, up to 10 redirects deep. It only accepts redirects to “http:” or “https:”, and only to ports 80 or 443. It does not accept redirects to IP addresses. When redirected to an HTTPS URL, it does not validate certificates (since this challenge is intended to bootstrap valid certificates, it may encounter self-signed or expired certificates along the way)."

When you opened this thread in the Help section, you should have been provided with a questionnaire. Maybe you didn't get it somehow (which is weird), or you've decided to delete it. In any case, all the answers to this questionnaire are required:

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command:

It produced this output:

My web server is (include version):

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know):

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

Thank you for assisting us in helping YOU!

[Mad182]

You can't validate the certificate on another port, but you can validate it on standard port and then use it on any port you want, or use DNS validation instead.

[Bruce5051]

@Mad182

or use DNS validation instead

Definitely an option.
Here is the link for the DNS-01 challenge of the Challenge Types - Let's Encrypt.

[jjrushford]

Thanks, I’ll use this method so that Lets Encrypt may validate me.

[jjrushford]

Thanks for your suggestions. I have got a lets encrypt cert now using certbot and I have automatic renewals scheduled in cron using certbot.

thanks
John