Solved Custom FQDN Lets Encrypt renewal problem

[greychain]

3CX V16.0.8.9
Debian

My LE certs aren't renewing anymore, now I'm getting
Type: unauthorized
Detail: Invalid response from
http://my.domain/.well-known/acme-challenge/GX80BPJcLRiMWoJ86OS8lk5jyj7rBJtH4D-siSaLIwg

3CX uses 5001 not 80 port website so how can I get LE to renew the certs. Tried telling the router to map port 80 to 5001 but as 5001 is SSL it didn't work.

Do I need to use acme-DNS-certbot.

 

[cobaltit]

Custom FQDN's are not supported so I don't know that you'll get much help here. But I'm not sure why you would try to redirect anything to a 3CX port since 3CX isn't handling the SSL you are.

 

[NickD_3CX]

Hi @greychain !

This is one of the great benefits if you use a 3CX FQDN/SSL Certificate, all the renewals are handled automatically by the system and you don't need to worry about it.

I hope you figure it out, but just a reminder, if you don't you can always switch to using a 3CX FQDN.

 

[greychain]

OK fixed, couple of small issues.

In the /etc/nginx/sites-enabled/your-pbx file I enabled port 80 in the 2nd server section where it uses port 5000.
In my router I had to forward port 80 to the server, the certbot doesn't seem to use SNI so needed to physically point port 80 to server.

run the certbot renew command