Let's Encrypt support for custom FQDN

[Marcel Menk]

Hello everyone,
there is something which would make me as happy as most of the others I think, so I though it might be worth posting it here.

As of right now 3CX supports Let's Encrypt certificates on the 3CX internal domains. Having this feature on the custom FQDNs as well would be great. Software, like Certbot for example, supports the generation of Let's Encrypt SSL without the need to change the DNS settings prior to obtaining the certificate, so there should be a way to implement it within 3CX as well. Looking forward to eventually see this feature one day.

Cheers
Marcel Menk

 

[[email protected]]

+1

 

[Mike Hammett]

It seems silly to support LE for some domains, but not others.

 

[florink]

For this to be possible either the domain's DNS will need to be pointing to the server's IP beforehand or 3CX will need to be controlling the domain's DNS. The former needs to be manually done by the administrator so it's not practical and the latter is simply not possible.

 

[Mike Hammett]

For this to be possible either the domain's DNS will need to be pointing to the server's IP beforehand or 3CX will need to be controlling the domain's DNS. The former needs to be manually done by the administrator so it's not practical and the latter is simply not possible.

How is it not practical for the DNS A record to be pointed at the server first? That's an extremely trivial process in every DNS server out there.

 

[BrenttG]

How is it not practical for the DNS A record to be pointed at the server first? That's an extremely trivial process in every DNS server out there.

Indeed, any basic level admin with dns experience can handle this, and anyone who cannot handle this, probably shouldnt be building out a pbx.