Unsupported Custom FQDN with LetsEncrypt

[digivie]

Hello,

We currently are running V16 on Debian 9 with a custom FQDN and LetsEncrypt providing the certificates. Is this configuration possible on the V18 ISO installer or is a custom installation still required for this configuration? I have not been able to find a clear answer on this in the documentation.

 

[QueBall]

That would be considered unsupported. Figuring out and making the SSL certificate update process work would be entirely on you to figure out. You can manually manage the SSL certificate files. The automation part is up to you to self support. (or hire a developer/consultant willing to support this) It is not built in.

 

[Saqqara]

Use a custom fqdn, you can use any ssl provider - you have to manage the ssl certificate , 3cx will not

 

[ChrisC_3CX]

I know this might be considered obvious but, in addition to what has already been mentioned I do have to add that using a custom FQDN means that you will not only have to provide and manage the SSL certificate, but you will also need to manage the DNS for the FQDN.

 

[digivie]

I guess the question I'm asking is whether the V18 ISO allows us to directly manage the nginx web server and certificate files the same way a manual Debian installation does. We have been using 3CX this way for years, but we'd prefer to simplify our deployment by using the V18 ISO then reconfiguring the SSL certificate and FQDN ourselves.

We don't have any issues with managing this ourselves, I just want to confirm that it is possible.

 

[ChrisC_3CX]

Installing using the 3CX ISO will allow you to specify your custom FQDN and import the certificates upon installation. This is done during the web installation Wizard exactly as it was done with a manual install of 3CX in the past so you should be just fine.