Solved Migrate 3CX FQDN Hosted NFR to Licence Pro and FQDN

Status
Not open for further replies.

thetissot

Bronze Partner
Basic Certified
Joined
May 20, 2020
Messages
23
Reaction score
2
Hello,

We are using our licence NFR for internal and i plan to migrate to a commercial licence 16 channel.

How can i do to keep my FQDN if i buy another licence (because i can't release FQDN on hosted).

Thanks in advance.
 
If I'm not wrong It seems to me you just need to change the key license
 
On hosted version, i can't click on the licence on the dashboard...
 
you mean 3cx hosted ?
 
This question needs to be answered by 3CX Staff @JohnS_3CX perhaps
 
On hosted version, i can't click on the licence on the dashboard...

Correct - 3CX Hosted instances have some restrictions.
You cannot change the license from within the management console.
 
thanks for your reply ,

Do you have a solution for my case :
We are using our licence NFR for internal and i plan to migrate to a commercial licence 16 channel.

How can i do to keep my FQDN if i buy another licence (because i can't release FQDN on hosted).
 
One solution is to take a backup without License + FQDN, then release the FQDN from the 3CX Portal.

Reinstall using the backup and new key, and when you are asked for FQDN you can pick an FQDN and select the same one again.

*Note: There is no guarantee you will be able to pick the same FQDN once you release, so keep that in mind.


Your other solution (to avoid ever releasing your FQDN) is to:

1. take a full backup and kill cloud instance
2. restore backup on local vm
3. login and change key there (it will swap keys and keep the FQDN)
4. take new full backup and kill local instance
5. restore in cloud again (new vm with new key and old FQDN)

Now the FQDN will never be released, but you will have to do some extra work.
 
Thanks for the reply,

In the first solution you say : " release the FQDN from the 3CX Portal" on 3cxhosted it's not possible .

In the second solution you say "and kill cloud instance " how to kill 3cx hosted cloud instance ?
 
@thetissot
Yes correct if you have a hosted machine with 3cx ( which you have right now ) you can not release the FQDN as this will cause ghost entries on our hosted platform and I think this makes sense.
In order to be able to release the FQDN, the Instance has to be first deleted.
Do you want to proceed with that option ?
If so, please proceed with this : https://www.3cx.com/community/threads/delete-instance-hosted-by-3cx.75573/
 
  • Like
Reactions: JohnS_3CX
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,962
Messages
589,993
Members
164,867
Latest member
swegner