Migrating to 3CX Hosted from On-Prem Hosted VM with Custom FQDN

[DA Systems]

We are attempting to restore a backup from an existing self-hosted 3CX v20 Update 8 instance that uses a custom FQDN to a new 3CX-hosted deployment.

However, when we upload the backup file through the 3CX portal, the upload fails with an "Invalid FQDN" error.

Steps performed:

• Created a full backup of the existing 3CX PBX.
• Unlinked the existing FQDN from the 3CX portal.
• Started the process of converting the system to a hosted deployment.
• Attempted to upload the BACKUP.ZIP file during the restore process.
• Received an "Invalid FQDN" error when uploading the backup.

Could you please clarify whether the xxxxxxxb.xml file within the backup needs to be modified to include a new FQDN and license key before the restore?

If so, what should be specified for the FQDN, considering that the system will be hosted by 3CX and we understand that a new FQDN will be assigned during the hosting process?

Any guidance on the correct migration procedure would be appreciated.

 

[Alphabetic]

I believe you're going to have to change to a 3CX FQDN before you attempt the migration.

 

[NikosK_3CX]

Can you please speak with your partner in order to raise a ticket with us to assist you?
You cannot use a custom FQDN in a hosted environment by 3CX.
You will have to proceed with a fresh installation and restore the backup we will provide you with post-installation
by using a remote location.

 

[DA Systems]

How do we change the FQDN to a valid 3CX domain?

 

[Alphabetic]

How do we change the FQDN to a valid 3CX domain?

It used to be possible in v18, not sure if its possible in v20 (Not supported anyway) - There may be other forum posts on how to do this. As @NikosT_3CX said - 3CX will have to edit your backup for you.

I've never done it, but I think you'll have to first take a backup without backing up the license key and FQDN read this

Maybe there are other threads on this forum that could help.

 

[Evolute IT]

How do we change the FQDN to a valid 3CX domain?

If you're unsure, we can assist with the change. We've done it many times.

 

[DA Systems]

I have backed up the config via CMD - with FULL and without LIC,FQDN - the portal says it is invalid. And edited the Db.XML from within 7-Zip. with '0' and 'companyname.3cx.uk' same....

Can't start from scratch, as we have users preconfigured...

 

[bitn2]

You can take the normal backup from gui and need to edit the xml within the container, dont unzip it. Change fqdn to the new one and change the key.

 

[Alphabetic]

You can take the normal backup from gui and need to edit the xml within the container, dont unzip it. Change fqdn to the new one and change the key.

Curious about this cos i've never done it.

but surely he cant change it to the new one until he's gone through the release FQDN, reinstall and created a 3CX FQDN?

Or are you saying you can stick any old 3CX FQDN in this XML with your key and it'll go off and bind?

 

[bitn2]

Curious about this cos i've never done it.

but surely he cant change it to the new one until he's gone through the release FQDN, reinstall and created a 3CX FQDN?

Or are you saying you can stick any old 3CX FQDN in this XML with your key and it'll go off and bind?

No, you need to release the old fqdn from the licence and install it with the new 3cx fqdn in the cloud. after that you can restore with the new fqdn from the old backup.

 

[DA Systems]

I wish it were that simple,

You can take the normal backup from gui and need to edit the xml within the container, dont unzip it. Change fqdn to the new one and change the key.

How do you know which FQDN it will change to?

 

[bitn2]

I wish it were that simple,

How do you know which FQDN it will change to?

You need to migrate your licence to the cloud and choose a 3cx fqdn. This fqdn you can use to restore your backup afterwards

 

[DA Systems]

Our reseller has said that it has been done, how do we choose a 3cx fqdn - (They don't seem to know what they are doing)

 

[Alphabetic]

You need to migrate your licence to the cloud and choose a 3cx fqdn. This fqdn you can use to restore your backup afterwards

Can you take a backup without key and fqdn, release fqdn, "Install to hosted" then restore your backup? Or does the 3CX FQDN have to exist outside of hosted and then a backup/restore in to hosted?

Anyway..

If its the latter... I just did these steps to change my FQDN if it helps @DA Systems

- Backup 3CX via CMD without FQDN and Lic
- Release FQDN
- Reinstall 3CX and use the "Install" button from 3cx customer portal to deploy to self-hosted, run through setup to generate url
- Use URL to install blank 3CX with your new FQDN
- Upload your backup to your new 3CX (WinSCP)
- Make sure 3CX up to date then restore your backup

Then I guess take your full backup, migrate hosted?

 

[bitn2]

switch to hosted... The fqdn will be chooses during the wizard.

 

[Alphabetic]

switch to hosted... The fqdn will be chooses during the wizard.

But at this point he doesnt have his backup with his 3CX FQDN will he?

 

[DA Systems]

This is where it fails over

*
No. - It will ask you to choose your own FQDN - amazing, but now to update our configuration
Yes - the backup loaded then, (see below)

 

[Alphabetic]

This is where it fails over

View attachment 51791*
No. - It will ask you to choose your own FQDN - amazing, but now to update our configuration
Yes - the backup loaded then, (see below)

View attachment 51792

See my previous comment.

 

[bitn2]

I’ve never done this with a 3CX-hosted installation. I think the procedure you described is the correct one. I’m just not sure if you can restore a backup without an FQDN and license; I believe that needs to be adjusted in the XML file beforehand.

 

[Alphabetic]

I’ve never done this with a 3CX-hosted installation. I think the procedure you described is the correct one. I’m just not sure if you can restore a backup without an FQDN and license; I believe that needs to be adjusted in the XML file beforehand.

Me neither

@DA Systems

humour me, do this.

- Backup 3CX via CMD without FQDN and Lic
- Release FQDN
- Reinstall 3CX and use the "Install" button from 3cx customer portal to deploy to self-hosted, run through setup to generate url
- Use URL to install blank 3CX with your new FQDN
- Upload your backup to your new 3CX (WinSCP)
- Make sure 3CX up to date then restore your backup
- Then take a full backup, trash this machine, go through setup of hosted install and restore this backup