3cx hosted installation,how to renew certificate on custom FQDN

[CHR_T]

Hello,we use self hosted 3cx installation(windows) ,with custom FQDN(not 3cx) in our DNS,and a wildstar certificate.
We plan to migrate the installation to 3cx hosted.
Assuming we keep the same FQDN,how will we able to renew our certificate every year?
I suppose we will not have ssh access to the 3cx hosted linux,in order to replace the certificate files.
Thanks

 

[NicholasP_3CX]

You can only use a 3CX FQDN with the 3CX hosted platform.

 

[CHR_T]

Thank you for clear reply.So,during the migration procedure,we will be asked to keep our FQDN,or to create a new 3cx FQDN.?
We will select 3cx FQDN,and load our backup?Or the backup should be created without our FQDN?

 

[NicholasP_3CX]

Since you will be restoring from the backup which contains your FQDN and license key, you will be blocked from restoring to a hosted by 3CX instance.

You will need to have an existing system with a 3CX FQDN. I can see however that you already have a key with a 3cx.gr FQDN activated on the hosted. Is it this PBX or another one?

 

[CHR_T]

It is another one,on premise hosted(windows) v18. with our FQDN ourdomain.com
So how can we proceed in this case?

 

[NicholasP_3CX]

As you are in Version 18 you are in luck.

1. Make sure that you are on Version 18, Update 9a
2. Make sure you have a system owner extension with a unique email address, and have VERIFIED access to this accounts web client (log in to it before the migration)

• Follow the steps essentially from this guide about the checklist https://www.3cx.com/blog/releases/v20-upgrade-checklist-faq/

Now, before you proceed with the actual migration.

1. Take a backup of 3CX without the FQDN and license key.
2. Download your backup to a safe location (example your PC)

Now to the migration.

1. Log in to your portal of 3CX. portal.3cx.com
2. Release the FQDN from your subscription under My Systems
3. Proceed from the portal, to install a FRESH installation of a version 20 system.
4. Ignore the option to restore from a backup, you will be creating a new instance, with a new 3CX FQDN
5. Once the installation has completed, you will be able to login with the NEW system owner account.
6. Configure the storage settings of the system. You will be uploading your backup to this location.
7. Once it is configured and your bckup is uploaded you will then be able to restore this configuration.
8. Wait for the confirmation email, and your old system with new FQDN will be ready.
9. Reprovision any phones that may be pointing to the old FQDN and off you go!

 

[CHR_T]

Thank you for your detailed information.
We already have a hosted v20 licenced installaton,with 3cx FQDN(the one you mentioned before under my account).
It has only 3 users(system owners) and still no other configuration.
We want to migrate the onpremise installation(Version 18, Update 9a,custom FQDN) to that existing hosted above.
Let me know,if the below steps are ok.
1)Backup the onpremise installation,without the FQDN and license key
2)Login to the hosted installation,configure the storage,and restore the backup from step 1
3)have system with 3cx FQDN,but with the old configuration

And if yes,final question
Both systems (onpremise v18 Update 9a and hosted v20) have 3 identical users(name/mail, system owners).
what will happen if i restore the backup from onpremise to hosted(as described above)

 

[bitn2]

Both systems (onpremise v18 Update 9a and hosted v20) have 3 identical users(name/mail, system owners).
what will happen if i restore the backup from onpremise to hosted(as described above)

You need different email addresses. They have to be unique.

 

[NicholasP_3CX]

One of our main requirements is for users with web access to the system to have a unique email address, as this is now tied to the 2FA autentication.

If a user has a duplicate emails address (from a migration from V18) then a user who loses their password will NOT be able to retrieve this. This is especially an oopsie if this is a system owner extension!

So ESPECIALLY the System Owners need to have a unique email address. Once these are sorted out, the users can be given a unique email address once you log in to the admin console.

 

[CHR_T]

The case is, system 1 (hosted v20) has user1,user2,user3
system 2(onremise v18 9a) has also user1,user2,user3 (identical names,mails,extensions,different passwords, with system1)
Restore backup(without licence and fqdn) from system 2 to system 1.
Which users will "survive" at the final hosted v20?

1)6 users(3 duplicates?)
2)user1,user2,user3 from hosted v20?
3)user1,user2,user3 from onpremise v18?

 

[NicholasP_3CX]

Nothing will survive from the existing Version 20 configuration except the FQDN and license. The configuration of Version 18 will overwrite everything.

 

[CHR_T]

Hello again,i followed the steps,the restore completed successfully(from onpremise v18 to hosted v20),but every system owner does not have gear "admin" icon on hosted v20).
After searching,i think we missed(onpremise v18) to remove "console restriction from private ip only" prior from backup restore.
Is there any way to find a solution now?

 

[bitn2]

Hello again,i followed the steps,the restore completed successfully(from onpremise v18 to hosted v20),but every system owner does not have gear "admin" icon on hosted v20).
After searching,i think we missed(onpremise v18) to remove "console restriction from private ip only" prior from backup restore.
Is there any way to find a solution now?

The support can help you in this case