We have one of our early 3CX clients that has still been using a custom FQDN & 3rd party SSL cert for their 3CX install, since it was originally setup before 3CX was offering their FQDNs and SSL certs via Lets Encrypt. We have changed FQDNs for other clients previously - always taking a 3CX backup but excluding the license info, uninstalling 3CX, then re-installing the same version, restoring from backup, then entering the license key & selecting the FQDN we want to use.
However, I'm going through this same process and after entering the license key, confirming the public IP address, and verifying it is static, I'm being forced to upload my certificate .pfx file. The whole point of this exercise is change the FQDN and have 3CX generate a Lets Encrypt certificate. The license is valid - it just renewed last week and I verified it is showing valid & active both in the partner portal and on the 3CX install before I took the backup & uninstalled. What am I missing?
Thanks!
However, I'm going through this same process and after entering the license key, confirming the public IP address, and verifying it is static, I'm being forced to upload my certificate .pfx file. The whole point of this exercise is change the FQDN and have 3CX generate a Lets Encrypt certificate. The license is valid - it just renewed last week and I verified it is showing valid & active both in the partner portal and on the 3CX install before I took the backup & uninstalled. What am I missing?
Thanks!
This was the first time we've gone through changing the FQDN since 3CX implemented the requirement to log in to the customer portal and release the old FQDN before restoring
