Solved Can't Restore V15.5 SP6 backup with Clean V16 install or do a clean install at all!

[theMightyMacBoy]

Posted on Reddit first, now posting here, because this seems to be an issue with 3CX since I cannot setup a PBX at two sites, with very different networks and server hardware across both OS options....

I am trying to upgrade to V16 and am running into some issues. We use our own FQDN and our own SSL certificate, yet the V16 web configuration tool is trying assign me a FQDN (or it seems) . I am not able to proceed past trying to complete the restore. See this album for screenshots.

This is a fresh Server 2016 VM with the same IP address as the old server. I have updated 3CX many times in the past and have had no issues with the restore. Is this a V16 bug?

Edit: In the process of installing v16 on Debian and going to try my restore on there. Wish me luck.
Edit2: Getting same error with Debian. Even getting same error when I try to use one of my other reseller licenses. Spinning something up at home in my lab to test from a different environment.
Edit3: Getting same error with Debian clean install with brand new license key. Most certainly has to be an issue with 3CX's activation servers. Now that it's almost 1:30am Eastern, I guess I will try in the morning again. If anyone can try to spin up a PBX on Linux or Windows and see if it works for you that'd be awesome. I am without a PBX until I figure this out. Live and learn

 

[AWS2P]

Hi , i'm suspecting a problem between 3CX and let's encrypt because i've got exactly same error message on let's encrypt renewal process on a always running v15.5 3CX on premise.

 

[pact]

We're also doing a client upgrade right now and getting this error, both 15.5 and 16.0. Have 12 hours to resolve this now before our client is back using it for Monday Morning....

@YiannisH_3CX @Nick Galea

 

[theMightyMacBoy]

I was able to get a clean install done. After the SSL generation failed a few times, it finally gave me an option to use self assigned. (This was using a demo key I have + a 3CX FQDN) . I was unable to restore my backup from that instance because of the license + FQDN mismatch. I am currently trying to get a clean install done with the production license key + custom FQDN. I will report back. I'm preaching to the choir, but we all need to get this fixed. I'm down to 23 hours until I have users in the office that will want to make phone calls.

 

[netropolix1]

Joining the club here...
made a backup, installed V16, tried to upload backup, hangs on creating FQDN en cerfiicates.
Also using our own FQDN and certificate.I have about 3 hours left untill i need to have this up and running.

 

[pact]

Given no response yet from 3CX I've fallen back to using the temporary self signed certificate.

From the limited testing we've done,

• Local Phones connect, but cannot be provisioned (as self signed certificate isnt trusted)
• Local 3CX Apps connect
• SmartPhone apps connect
• Web interface can only be managed via IP, using FQDN gives HSTS error which Chrome/FF won't allow bypass.

3CX also provide this note, so I guess we just have to trust the SSL will replace on its own;

Warning!
Temporary self-signed SSL certificate created. You can proceed and complete 3CX installation setup. Periodically 3CX will automatically launch a background certificate request process to get your certificates from the Certificate Authority. When the signed certificates are downloaded, the admin will be notified via email and the self-signed certificates will be replaced.

 

[NW Computing]

Thought I'd just let you know @pact That we are in the exact same scenario at the moment.
Second time this year the activation servers are playing up.

 

[bdarcyevans]

+1
New Windows Server 2019 VM. Using restore from 3CX backup method (existing 3CX FQDN). Unable to create. Tries and eventually times out. Connectivity otherwise OK.

 

[pact]

@bdarcyevans yes, we've still not had a word from 3CX. So for now go ahead and check the 'Generate temporary self-signed certificate' and the 3CX instance will restore.

You will then get the info above stating how the SSL will renew when it begins working again.

 

[pact]

Just a follow up, I've now had contact from 3CX, they are aware of the issue and are working on sorting it out, no ETA yet.

 

[bdarcyevans]

Thanks @pact. Since I'm not in a rush I'm just going to wait. Luckily, I built a new VM for v16 so I'm able to shut it down and boot the v15.5 back up.

 

[mace]

We are having same issue. very bad on 3CX side for not providing any answer or a temporary solution for the time being

 

[NickD_3CX]

Hi everyone!

There was an issue preventing the generation or renewal of SSL Certificates, which since been addressed.

Please give it another try and it should be fine.

 

[pact]

And we're back and operating, thanks for the update @NickD_3CX