SSL renewal - Custom FQDN

[jskinner97]

Hi,

I am trying to install Certbot on the 3CX to manage custom FQDN renewals via Lets Encrypt. I have managed to successfully create a new CRT:

Congratulations! Your certificate and chain have been saved at:
/etc/letsencrypt/live/pbx.lpr.midlandnetworks.co.uk/fullchain.pem
Your key file has been saved at:
/etc/letsencrypt/live/pbx.lpr.midlandnetworks.co.uk/privkey.pem
Your cert will expire on 2021-02-06. To obtain a new or tweaked
version of this certificate in the future, simply run certbot again
with the "certonly" option. To non-interactively renew *all* of
your certificates, run "certbot renew"

However, I cannot access that file directory unless I change it to ec2-user:ec2-user - but then it will not let me download those files.

Has anyone been able to install certbot to get LetsEncypt certificates? If so, please could you help!

We CANNOT use 3CX FQDNs due to our business, and we manage DNS ourselves with multiple fail overs.

Thanks!

 

[jskinner97]

All sorted! Please ignore

It works, just had to restart the NGIX server

 

[cobaltit]

We CANNOT use 3CX FQDNs due to our business, and we manage DNS ourselves with multiple fail overs.

Can you explain this statement? I've yet to see anyone actually provide a reason they CANNOT use 3CX FQDN. Lots of reason why they want to use their own FQDN but none that the 3CX FQDN wouldn't work for (other than cosmetic)