Solved FQDN Problems - 3CX to Custom

[Mike Hammett]

I accidentally purchased a standard license instead of a professional license. I upgraded the license.

I found the documentation at https://www.3cx.com/docs/fqdn-management-allocation/ telling me how to release the FQDN from the key. I did that, but a reinstall skips the FQDN setup and just puts in the old one.

How do I get to a point where I can get a new FQDN?

 

[Saqqara]

Is there any reason you want to have a new 3cx FQDN

Remember any remote clients (phones, iOS and Android clients) will have to provision along with any internal devices using fqdn

 

[Mike Hammett]

It's a brand-new installation. No configuration of any kind, other than what the initial setup process does.

I don't want a 3CX FQDN involved. I'm selling my service, not 3CX's. I want to push my brand, not 3CX's.

 

[Saqqara]

If you want a new fqdn you have to do a backup without the license and fqdn, uninstall 3cx, release the fqdn via the portal and finally reinstate your the backup

Note: copy the backup to a new folder from the standard 3cx folder, else it will be deleted when uninstalling

 

[Mike Hammett]

No backup necessary and I have reinstalled the VM. I've also released the FQDN in the portal, but as I said in my original post, the setup process didn't even ask for FQDN-related information, it just used the old information.

 

[Mike Hammett]

I wiped it out again and tried again and now it works.

No idea why it didn't work the last time I tried it.

 

[YiannisH_3CX]

Glad to see the issue has been resolved and thank you for updating the thread.