Upgrade to V18; Now wish to switch FQDN

[epodworksnet]

I recently built a new VM running 3CX Debian to run V18. I restored the config using the backup from Windows V16. All is good.

However, what I would like to do is drop the private FQDN customer.example.com in favor of 3CX supplied FQDN so that I no longer have to manage the certificate.

I do realize that once the re-install is completed you can't change the FQDN, however, when I performed the re-install I did not get any option to change this string.

I also don't see the "disconnect" link in the FQDN Field in the 3CX System Management Portal (https://portal.3cx.com). Anyone have any ideas how to make this adjustment?

 

[cobaltit]

I believe you'd have to take a backup without license key/fqdn and then restore to get that option.

 

[Saqqara]

Backup 3cx without license / fqdn , release the license in the customer portal, then reinstall 3cx

 

[epodworksnet]

OK. I will try that option. How Does this "disconnect" the FQDN from the license? Is that part of the installation process?

Thanks so much!

 

[epodworksnet]

Ran into a snag I get this error "The backup version 18.0.4.955 is newer than the PBX version 18.0.3.461. You can restore this backup only with PBX version 18.0.4.955 or newer.".

It would seem the downloaded ISO of 3CX Linux from the Portal is slightly old (18.0.3.461) than the running V18 after install as it got upgraded after the restore process. When I first logged into the 3CX instance the status showed the "Your System is Update to Date". Later on, I see an update was pending "Update 4 BETA" which I processed. Next time I'm NOT going to upgrade so fast!

The work around I'm going to implement is go all the way back to V16 and backup that version without a License and FQDN and see how that works!

 

[cobaltit]

You can't. It would appear that you upgraded to the Beta version and the download is the latest stable. You'd have to use your original V16 backup or wait will Update 4 becomes final.

 

[epodworksnet]

Going back to the V16 Backup W/O License did not work either as you get a prompt for "Please select the path to your Certificate file (.pem, .crt or .pfx only) during the backup restore process. The whole idea here is to drop the private FQDN in favor of 3CX supplied FQDN so that Security Certificates are managed by 3CX.

I think the issue as soon as I add the OLD license key it gets the current FQDN from the backend. I believe the issue is you need to "disconnect" or unlick the existing FQDN which is not possible as this option is missing from the portal.

I validated this by selecting another License Key that I have that does not have an FQDN assigned (private or 3CX) and this works as expected. This alternative License now shows <customer>.east.us.3cx as the FQDN. I'll have to get with 3CX how to "disconnect" this license that worked so I can switch back to the OLD license or just upgrade this alternative license key.

 

[epodworksnet]

You can't. It would appear that you upgraded to the Beta version and the download is the latest stable. You'd have to use your original V16 backup or wait will Update 4 becomes final.

Thanks, Yep

You can't. It would appear that you upgraded to the Beta version and the download is the latest stable. You'd have to use your original V16 backup or wait will Update 4 becomes final.

Thanks for your post. I just realized that and updated my prior post. Again, thanks so much for your help.

 

[Saqqara]

OK. I will try that option. How Does this "disconnect" the FQDN from the license? Is that part of the installation process?

Thanks so much!

you have to log into the customer portal , to release the fqdn https://www.3cx.com/docs/fqdn-management-allocation/

 

[epodworksnet]

Thanks for the try. I've already looked at this web page documentation, however, this appears to no longer match as the portal has been recently updated. What I see is a pencil icon to click to get access the details for the license; then on this web page you can unlink the FQDN using "disconnect" web link near the FQDN field. This is NOT present is not in my case as I think this has something to do with the fact that I used a private FQDN. Some additional step is required that I am missing.

 

[epodworksnet]

to 3CX: Am I missing something or do you need to update https://www.3cx.com/docs/fqdn-management-allocation/?

 

[epodworksnet]

Looks like you can ONLY disconnect the FQDN when you LOGIN to the partner or customer account with the eMail Address associated with the License. This is a change in 3CX policy effective with the new Portal as I understand it.