Solved Use Your Own SSL & FQDN Certificate

[vankampen]

Hi, I have a system with a company.my3cx.nl address. I would like to change that to our own SSL & FQDN certificate. Is that possible?

 

[SweetAction]

V18: Take a backup without KEY/FQDN, reinstall and choose FQDN during install
-Make sure to release the FQDN from the key in the 3CX customer portal

V20: Same, but fresh install and configure from scratch

 

[vankampen]

-Make sure to release the FQDN from the key in the 3CX customer portal

Before or after the backup?

 

[SweetAction]

Before or after the backup?

After you shutdown the old server/uninstall the 3CX software (store the backup somewhere safe) before you install/start the restore process.

 

[vankampen]

Thx

 

[vankampen]

After you shutdown the old server/uninstall the 3CX software (store the backup somewhere safe) before you install/start the restore process.

Ha, this worked like a charm. Everything up and running and the Firewall checker is happy.
Only my account puts port 5001 behind the FQDN, which is not needed in my case. But the management console and webclient works, they don't require the port.

 

[OlegR_3CX]

Only my account puts port 5001 behind the FQDN, which is not needed in my case. But the management console and webclient works, they don't require the port.

Not sure if this topic is over?
Does it mean you want to use 443? What do you mean the Webclient dont need to use port?

 

[vankampen]

I mean https://myphone.mycompany.com/webclient/#/login goes to the webclient, and https://myphone.mycompany.com goes to the management console both locally and through the internet. It does not need the port on the FQDN. Internally 3cx is using port 5000. Pfsense obtaines the certificate from LetsEncrypt, decrypts the traffic in the reverse proxy and routes the traffic to the 3cx server on port 5000.
But when I look in My Systems it shows https://myphone.mycompany.com:5001. I don't know if there is anything that will break if the 5001 is mentioned there, and not in the actual FQDN. I guess not.

Thanks for your help.

 

[bitn2]

I mean https://myphone.mycompany.com/webclient/#/login goes to the webclient, and https://myphone.mycompany.com goes to the management console both locally and through the internet. It does not need the port on the FQDN. Internally 3cx is using port 5000. Pfsense obtaines the certificate from LetsEncrypt, decrypts the traffic in the reverse proxy and routes the traffic to the 3cx server on port 5000.
But when I look in My Systems it shows https://myphone.mycompany.com:5001. I don't know if there is anything that will break if the 5001 is mentioned there, and not in the actual FQDN. I guess not.

Thanks for your help.

That means your pbx is installed with 5000 and 5001. But your proxy in front of this is using 443. That scenario isnt supported and you are in your own with any problems regarding this.

 

[vankampen]

That means your pbx is installed with 5000 and 5001. But your proxy in front of this is using 443. That scenario isnt supported and you are in your own with any problems regarding this.

Okay, good to know, thanks

 

[OlegR_3CX]

Perfect! We will now close this thread.
Have a great day