3cx.co.uk server - how to reinstall?

[rscott101]

We have a server using a 3cx.co.uk domain, but appears we're unable to reinstall now you've discontinued use of that domain???

Have a backup, but it's completely useless as there's no way to change the FQDN. So looks like I need to reinstall from scratch

 

[Guillaume Bourgeois]

Hello,

I'm not sure where you got your information, but it is not correct. If you have a license with the FQDN *.3cx.co.uk, as long as the FQDN is not released, you can reinstall and restore using the same FQDN (and license).

The fact that 3CX no longer allows the use of the FQDN *.3cx.co.uk only affects new registrations.

 

[rscott101]

Unfortunately, we accidentally released the FQDN. So now we have a backup we cannot use.

It looks like the only solution is:-
1. Keep the old server running.
2. Set a local hosts entry on my laptop to map the old hostname to old IP address
3. Create a brand new, empty host.
4.Manually copy over the configuration to the brand new host.
5. Look for a replacement for 3cx which offers FQDN portability and stability. Too many things broke without clear warning in the upgrade from V18 to V20. Our management have lost confidence in the product.

 

[Guillaume Bourgeois]

Unfortunately, we accidentally released the FQDN. So now we have a backup we cannot use.

Ah, that's different! Releasing an FQDN by accident involves several steps, including ignoring a warning. It's not straightforward. I believe it's more likely that the FQDN was by error released by the license owner, perhaps due to a misunderstanding.

You cannot blame 3CX for this action.

However, if you're willing to change your FQDN, I can certainly help you modify it directly in your backup.

 

[rscott101]

The warning is the same for both .3cx.uk and .3cx.co.uk domains - it doesn't mention that it's not possible to re-register a .3cx.co.uk domain.

f there's a way to change the FQDN in the backup, that would be great - then I can restore onto a fresh install.

 

[Guillaume Bourgeois]

3CX states that if you release your FQDN, there's a chance you might not be able to recover it. This should be reason enough NOT to release it.

If your backup is not encrypted, upload it to a cloud service. Send me the link privately so I can download your backup, and I'll take care of it. Please send me a preferred FQDN prefix privately.

 

[rscott101]

Just posting a huge public thank you to Guillaume for modifying my backup so I could restore to the new server.

 

[Guillaume Bourgeois]

Heh heh!
That makes me happy!

Don't release the FQDN anymore.
Unless you no longer want the FQDN. Hehe!

 

[Guillaume Bourgeois]

@rscott101
If you're satisfied, please tag your PBXs with our Partner ID 243448.
When it's time to renew your license, contact me—you have my email ( If we are tagged, we will contact you 45 days before expiration to remind you to renew. )
This won't affect you, and for us, it makes a difference in achieving our annual objective.

 

[Guillaume Bourgeois]

It's remarkable how many people need this type of intervention. I receive quite a few private messages asking me to perform this operation.

Each scenario I've been privately approached with was legitimate, which is why I'm happy to assist.

However, there's no secret. @SteveITS and I discussed this openly in another forum thread.
I simply use Linux command lines. I'll share the method I use, hoping it might help those who hesitate to contact me.

Other methods might work too, but I'm sharing the one that has been successful for me.
Needless to say, this is not supported by 3CX, so there's no point in opening a ticket with 3CX if it doesn't work for you.

You will need to have zip and unzip installed on your Linux environment where you'll be performing the operation.
+
Have an unencrypted 3CX backup ready.

I don’t have time right now to write a detailed procedure, but those who are familiar should understand.

# Write the name of the compressed 3CX backup folder into a variable.
Backup3CXzip=(*.zip)  # Replace (*.zip) with the name of your 3CX backup file. If it's the only .zip file in the directory, (*.zip) will select the first .zip file it finds in the current directory.

# Automatically find the .xml file at the root of the backup.
XmlFile=$(unzip -l "$Backup3CXzip" | awk '/^[ ]+[0-9]+[ ]+/{if (!match($4, /\//) && $4 ~ /\.xml$/) print $4}' | head -n 1)


# Decompress only this file.
unzip -o "$Backup3CXzip" "$XmlFile" -d ./ &>/dev/null && chmod +w "./$XmlFile"


echo "You can now edit the decompressed xml file with a text editor like nano."

You can now edit the decompressed xml file ( licence, FQDN ect.. )


When finished, recompress the XML file:

zip -j -u -q "$Backup3CXzip" "$XmlFile"

Have a great day, everyone!