V20 - Change FQDN

maxihoster

Bronze Partner
Basic Certified
Joined
Jan 24, 2024
Messages
1
Reaction score
0
Hello,

I dont' found anyway to change my fqdn for my 3cx install!
The problem is when creating a backup with V20 we can't select option to create backup without license and FQDN information!

Trying to release FQDN into my 3cx portal console and reinstall a new 3cx importing backup but the license and fqdn are include into backup so the problem persist.

Someone have a solution for that?

Regards
 
Depending on the license status, there may be a way to utilize the already-activated PRO/ENT license.
You will need access to the registration email to release the FQDN and transfer license ownership to the new owner.
After the above actions, it may be possible to use the license for a new installation.

To provide you with more detailed guidance, please contact our customer service team and provide the license key number so that they can check and assist based on the license status and requirements of the new system that you want to use it for.
Will do!
Thanks!

Edit: do I need to purchase support for this? Outside of the forum, Ive never contacted support.
 
Will do!
Thanks!

Edit: do I need to purchase support for this? Outside of the forum, Ive never contacted support.

You do not need to purchase support to contact our customer service team for licensing inquiries.
You can reach our customer service team by filling out the form on the 3CX website: Contact Us.
 
Last edited:
Awesome. I appreciate it
 
  • Like
Reactions: IrinaP_3CX
How can I restore a backup in version 20 with the same FQDN but a difference licence key?
 
You can replace the license key after the restore. Or before the backup.
 
How can I restore a backup in version 20 with the same FQDN but a difference licence key?
You can replace the license key after the restore. Or before the backup.
You will need to ensure that the destination key does not have an FQDN already assigned to it, and that it is not an NFR, or trial key.
 
How do we "correctly" handle the situation where we have 1 customer who is growing, and another one who is preparing to go out of business? In the past, we have swapped licenses when one customer shrinks, and another grows since the customer who is shrinking no longer needs that concurrent call capacity. We also noticed that you removed the workaround from the parameters in the latest release candidate of v20 update 3. Should we bother asking you to bring that back since there are several legitimate use-cases where the license key and the FQDN should each be able to be altered.
 
  • Like
Reactions: providencetg
You can't restore a backup made without a FQDN anymore, so the backup cli won't be helpful at all.

You need to create a normal backup of your V20 3CX and downlaod it.
Extract the contents of the zip, open the xml in the root folder and edit the <license> or <fqdn> xml contents accordingly, then re-zip it or replace the xml in the zip file and restore the pbx with the modified backup.

I only tested this with a complete reinstall, not restoring from the 3CX backup interface,

Just had to do this, even a license change is possible this way, but would also be possible in the webinterface.
 
Last edited:
We are facing the exact same issue. Now our entire 3CX phone system is down. Please advise on how to change the FQDN on a running server. Is there a command we can use?
 
We are facing the exact same issue. Now our entire 3CX phone system is down. Please advise on how to change the FQDN on a running server. Is there a command we can use?
No, there isnt any command. Backup/Restore is the way to go.
 
  • Like
Reactions: Evolute IT
Hi 3CX Support,

In this case, now 3CX version 20 update 3 Build 806 can not backup without License Key Information, FQDN & Conference.
How to >> customers want to change FQDN name within old Config file, call history data.

Thank you,
 
Yeah, I just ran into this issue too. Trying to upgrade from V18 to V20 and it broke a lot of programing. We setup a lab system reprogramed it now we can't remove LIC or FQDN from the backup of the lab system.
 
Last edited:
Hi Charles,

We’re currently facing a similar situation where we only need to update the FQDN. The FQDN is customer-specific, but due to a recent name change on their side, we’re required to update the FQDN to reflect this change.

From what I’ve gathered in this forum, it seems a fresh install may be necessary. Could you please confirm whether the following approach would be viable:

  1. Create a new 3CX instance using the correct FQDN under a free license.
  2. Unbind the FQDN from the existing paid license via the 3cx Portal.
  3. Apply and replace the paid license (now unbound) to the newly created instance.

I attempted to replicate this using two free licenses for testing purposes, but as expected, a free license cannot replace another free license—so I couldn’t validate the process.

If this works, then exporting extensions and re-importing back, and manually configure the config will me minor (Well in my case at least).

I’ll wait for your confirmation or any additional guidance.

Thank you.
 
  • Like
Reactions: Evolute IT
Based on the information received from the link:

The “Replace Key” function within the Admin Console remains available for other use cases, such as upgrading a Free license to a Commercial license. However, commercial keys cannot be replaced under any circumstances.

So from my understanding:
- You can replace a Free license with a Commercial license.
- You cannot replace a Commercial license with another Commercial one.

However, in my case, the goal is simply to replace a Free license to a Commercial one. Based on the available information, I don't see any reason why this shouldn't be possible. If this cannot be done, then what will the reason be that the "Replace key" is still visible? It should've then said "Upgrade License".
 
Last edited:
@Morne Spies your understanding is correct -
- You can replace a Free license with a Commercial license.
- You cannot replace a Commercial license with another Commercial one.
 
Chiming in here as well because this change is beyond stupid. All I need to do is change the FQDN because my client merged with another and they want to use the new company URL. I don't want to have to COMPLETELY reconfigure the whole phone system for such a small change. 3CX has really jumped the shark.
 
Chiming in here as well because this change is beyond stupid. All I need to do is change the FQDN because my client merged with another and they want to use the new company URL. I don't want to have to COMPLETELY reconfigure the whole phone system for such a small change. 3CX has really jumped the shark.
Just modify the backup and restore... Its still possible to change the fqdn.
 
Chiming in here as well because this change is beyond stupid. All I need to do is change the FQDN because my client merged with another and they want to use the new company URL. I don't want to have to COMPLETELY reconfigure the whole phone system for such a small change. 3CX has really jumped the shark.
I absolutely agree with you. I have no idea what 3CX was thinking with this new UI. It has been utterly awful. Version 18 was great. I don't know why they had to mess it up so badly with version 20. When they went to version 20, it's like they took all of the features of version 18 and threw it into a box, shook it up, and splashed it onto a web page with features all over the place with no rhyme or reason as to why the features are where they are now. I will never get used to this convoluted web UI they have now. 3CX has certainly gone down since version 20 IMO. I fully anticipate finding an alternative solution using AI.
 

Forum statistics

Threads
111,953
Messages
589,910
Members
164,845
Latest member
tdzski5