Change of FQDN in version 20

[Oleksii]

Hi!

We have version 20 (Licensed version) installed on Debian on our cloud.
We need to change the FGDN for 3CX

We did it like this:
1. Made a backup in version 20
2. Removed the FGDN binding in the account for this serial number
3. Installed a new virtual machine with version 20
4. During installation, set the static IP address
5. Selected the backup file
6. Uploaded a certificate for the new FGDN in the form of a PFX

As a result, the certificate is installed, but the FGDN remains old.

How to change the FGDN and leave a backup of the system with the rest of the settings?

 

[SteveITS]

Officially, 3CX's way is to start from scratch and not restore.

I have seen posts referencing https://www.3cx.com/docs/backup-restore-command-line/ which may help you.

 

[fxbastler]

How to change the FGDN and leave a backup of the system with the rest of the settings?

This is not possible.

 

[Oleksii]

This is not possible.

But I did it

 

[fxbastler]

But I did it

No, definitely not. You described what you did, asked one question and that one is exactly what I answered. You wrote yourself that you reinstalled 3CX. Yes, you can keep a backup, but somewhere else - not on this 3CX. That would be illogical.

Otherwise, please ask a clear question. I think we are talking about different things.

Back to your problem.

1. Made a backup in version 20

Did you create the backup in v20 without FQDN and without license with 3cxbackupcmd? Has this been checked: is there no longer a <license>, <fqdn> or <certificate> tag in the configuration file in the backup?

 

[Oleksii]

I made a backup through the 3CX WEB interface.

In the v20 web interface, it is no longer possible to delete a license and FQND.
That is, this information was in a backup.

I saved the backup on another PC.
After that, I unlinked the FQND in my 3CX account.

When restoring from a backup on a new PC, there is no field for the license and FQDN.
I didn't use 3cxbackupcmd. I changed the backup file.

 

[Oleksii]

I have seen posts referencing https://www.3cx.com/docs/backup-restore-command-line/ which may help you.

Unfortunately, the 3CXRestoreCmd option does not work in version 20.
If I remove information about the license and/or FQDN from the backup, I could not restore the PBX from such backup file.
I get error during restore/installation.

If you edit the backup file, as I did yesterday, then the FQDN on the PBX changes, and it also changes in the subscription panel.

But at the same time, Push notifications do not work on Android.

 

[Miragetek]

Hi All, Changing the FQDN for an already configured system. IS possible,,, Completlyunsupported by 3Cx to the point that they say its impossible and a complete nightmare to perform.
I had to do it where a client that had a .co.uk domain.had an issue and needed a reinstall. .co.uk is no longer supported\registered by 3CX for their hosted solution so backup rendered useless. As the wizard askes you for domain info at the end of a reprovision and restore operation.

If you have a .co.uk domain for hosted 3CX, Never release it unless you have no other choice.

Short answer for the process ****** DANGER *******
take a backup of the existing system, download it and keep it safe.
Provision a new hosted environment using the new FQDN, using the restore from the old system as the base. If you have to do this process then it won't clash with the old one. --- Otherwise why are you doing this at all??? -----

once your new empty environment is up. Take a backup and name the file somethin-new so you don;t confuse the two backup files.

take a copy of New-backup and put it somewhere safe. This is in case anything goes wrong.
Unpack the XML file from the root of both backup zip files.

Use a file comparison tool to copy settings from the old to the new.
Do not overwrite any crypto hashes or keys in the new file = instant break...

after every so many copies (extension settings, phone book entries, etc.
Repack the updated XML file int the root of your working copy of the new backup (reason for making a safety copy elsewhere).
try and restore the backup to the new system.

If it works all good, continue making changes until everything is back.
Otherwise, overwrite the broken copy of the new backup with the safety copy and start again.

You will get there after several hours\days.
**** Good Hunting ******

 

[Oleksii]

Hi All, Changing the FQDN for an already configured system. IS possible,,, Completlyunsupported by 3Cx to the point that they say its impossible and a complete nightmare to perform.
I had to do it where a client that had a .co.uk domain.had an issue and needed a reinstall. .co.uk is no longer supported\registered by 3CX for their hosted solution so backup rendered useless. As the wizard askes you for domain info at the end of a reprovision and restore operation.

If you have a .co.uk domain for hosted 3CX, Never release it unless you have no other choice.

Short answer for the process ****** DANGER *******
take a backup of the existing system, download it and keep it safe.
Provision a new hosted environment using the new FQDN, using the restore from the old system as the base. If you have to do this process then it won't clash with the old one. --- Otherwise why are you doing this at all??? -----

once your new empty environment is up. Take a backup and name the file somethin-new so you don;t confuse the two backup files.

take a copy of New-backup and put it somewhere safe. This is in case anything goes wrong.
Unpack the XML file from the root of both backup zip files.

Use a file comparison tool to copy settings from the old to the new.
Do not overwrite any crypto hashes or keys in the new file = instant break...

after every so many copies (extension settings, phone book entries, etc.
Repack the updated XML file int the root of your working copy of the new backup (reason for making a safety copy elsewhere).
try and restore the backup to the new system.

If it works all good, continue making changes until everything is back.
Otherwise, overwrite the broken copy of the new backup with the safety copy and start again.

You will get there after several hours\days.
**** Good Hunting ******

I did about the same.
I replaced the FQDN in the configuration file in the backup.
Everything worked except for PUSH notifications and calls to mobile phones. As far as I understand, 3CX registers the FQDN during the initial setup. And she needs a config created on the portal. Also, version 20 requires records in the reverse DNS zone that correspond to the FQDN and must be resolved at the beginning of the installation. Also, version 20 does not have an internal domain name and an external domain name. They match and are not configured in any way from the web interface.
Perhaps I missed something and there is a workaround. But after 8 reinstallations, I did everything from scratch.
In fact, this is madness, since in version 18 everything was much simpler. And now you need to keep 2 zones in the internal domain.

 

[maxbas]

But I did it

could you explain how you did ?