To change FQDN for NFR license

[00raman]

Hello, I'm trying to change the FQDN for our NFR license key running on Debian v20. I have taken a backup with --options=CH,LIC,PROMPTS,FW,REC,VM and confirmed in .xml file that FQDN is not included, released the FQDN from license key. Built new VM, and restored the backup (without FQDN) but it doesn't ask to enter new FQDN and links to old FQDN and on license key, it shows the old FQDN.

Any help \ suggestions will be appreciated.

Raman

 

[TheodorosG_3CX]

Maybe this post here help you further as you need to release the FQDN first.

 

[Evolute IT]

confirmed in .xml file that FQDN is not included, released the FQDN from license key.

Maybe this post here help you further as you need to release the FQDN first.

They already did.

 

[TheodorosG_3CX]

Exclude the LIC from the backup as well, then create a clean installation and then restore the backup.

 

[paulodagraca]

Like TheodorosG_3CX and ConceptsWeb, already did mention.

-Create backup of the 3Cx server (you already have one)
-Make sure 3CX server is down/off, (not online).
-Remove FQDN from License key.
-Install NEW 3CX with licence key, and new FQDN
-Create a backup of the new 'empty' 3CX server, to get the XML file license and contact information.
-Modify the 'old' backup with license and contact information.
-File transfer backup to 3CX server
-Restore backup, all should be okay again with new FQDN

Paulo

 

[fxbastler]

my standard answer:

1. create a complete backup of the 3CX
2. save the backup outside of the 3CX
3. make sure it is complete (extracting it correctly should be enough)
4. make a copy of the backup
5. open the copy with Windows Explorer (for example)
6. extract the XML from the compressed file
7. edit the XML and replace the 3CX FQDN in all places
   you may need to adjust the FQDN in some other places, like databases in the backup, YMMV
   you may need to adjust other licensing information as needed, this depends on how it's configured by 3CX, you may have to experiment
8. drag the edited XML back into the backup
   this ensures that the backup is not discarded when 3CX is restored
   the way the file is assembled is important, simply unpacking and repacking all together won't usually work
9. reset 3CX:
   Debian - start /usr/sbin/3CXWizard -cleanup on the shell
   Windows: remove 3CX, delete the directory below ProgramData, reinstall 3CX
10. unlink your license from the old FQDN in the 3CX portal
11. maybe: start the 'install' for your now unlinked license with the new own FQDN in the 3CX portal so 3CX knows about the binding between your license and the new own FQDN, this creates a setupconfig.xml which should be unneccesary
12. start the 3CX First Time Setup Wizard, give it the backup and give it the certificate files if you use your own (you should have them)
13. set the ports back to how they were before

point 7 is it

With a little more effort, you can change even more things: system owners, passwords (or hashes), the license key, email server and so on.

Even though 3CX doesn’t officially support this, these possibilities still exist. Whenever I’ve actually helped someone with something like this, I haven’t published it in the forum - since now

 

[JohnS_3CX]

It's been a while now, but FQDNs are selected from the Portal, not the installation wizard like it used to be in V18.

Same deal as when you purchase a new key, you deploy from the Portal, you choose FQDN, we bind it at that point and generate a config XML for you (you can use your backup instead AFTER binding).

 

[00raman]

Thank you for your recommendations. I will try and report back.

 

[00raman]

Hello All,

Thank you for suggestions. I'm able to change the FQDN.

Steps followed
1. Take backup of existing 3CX without LIC, FQDN (and full backup just in case)
2. Disconnect the FQDN from license
3. Install the new 3CX with new FQDN and apply the license
4. Uploaded the backup without LIC, FQDN to new installed 3CX
5. Restore the uploaded backup.

Regards,

Raman

 

[Randall Caudill]

Does the license have to be expired before you can release the FQDN on a self hosted install?

 

[00raman]

No conditions, you can release it when you want to change the FQDN.

 

[Randall Caudill]

okay what about a normal active license?

 

[00raman]

Same for all licenses.

 

[Randall Caudill]

hmm well I dont see an option to release it on any of my licenses, not sure what I am missing.

 

[KyriacosS_3CX]

After the pencil icon you get this page:

 

[ICR10500]

my standard answer:

1. create a complete backup of the 3CX
2. save the backup outside of the 3CX
3. make sure it is complete (extracting it correctly should be enough)
4. make a copy of the backup
5. open the copy with Windows Explorer (for example)
6. extract the XML from the compressed file
7. edit the XML and replace the 3CX FQDN in all places
   you may need to adjust the FQDN in some other places, like databases in the backup, YMMV
   you may need to adjust other licensing information as needed, this depends on how it's configured by 3CX, you may have to experiment
8. drag the edited XML back into the backup
   this ensures that the backup is not discarded when 3CX is restored
   the way the file is assembled is important, simply unpacking and repacking all together won't usually work
9. reset 3CX:
   Debian - start /usr/sbin/3CXWizard -cleanup on the shell
   Windows: remove 3CX, delete the directory below ProgramData, reinstall 3CX
10. unlink your license from the old FQDN in the 3CX portal
11. maybe: start the 'install' for your now unlinked license with the new own FQDN in the 3CX portal so 3CX knows about the binding between your license and the new own FQDN, this creates a setupconfig.xml which should be unneccesary
12. start the 3CX First Time Setup Wizard, give it the backup and give it the certificate files if you use your own (you should have them)
13. set the ports back to how they were before

point 7 is it

With a little more effort, you can change even more things: system owners, passwords (or hashes), the license key, email server and so on.

Even though 3CX doesn’t officially support this, these possibilities still exist. Whenever I’ve actually helped someone with something like this, I haven’t published it in the forum - since now

Thanks for this information. I'll edit the backup XML file if needed