Issues after upgrade from v18 to v20, PWA App stuck in constant Disconnect/Reconnect Loop.

[bitprecision]

Hello,

First time poster, long time forum trawler.

We recently upgraded one of our clients from v18 to v20 on a cloud hosted Debian Server.

I went through the checklist that I found in the blog posts, although this was helpful it seems to be missing some key details.

The most important one is the setting of the Listening port for the PWA, on v18 this is set to 5001, in fact all our clients have this set, I am fairy new to upgrading 3CX and to get our upgrade completed we need to image our host with the latest Debian ISO + 3CX v20, We had taken a backup of our 3CX Tenant (Full Backup) and we restored this once the server image was completed.

Everything went smoothly until this morning, when all softphone users were unable to login to the PWA app, it was stuck in a constant Disconnect/Reconnecting loop and no way to stop it.



This was a bit of a head scratcher until I remove the port from the URL and was able to see the login screen again in the browser.

I was not aware that if you don't change the port as part of the server setup that this would occur, and as you are not able to reconfigure the PWA app I have had to uninstall and reinstall this for several end users, this is somewhat annoying, If the Check list had made a note about ensuring the ports were configured as part of the setup I would have done so, Yes this is partial on me for not paying much attention and just moving thought the server setup too quickly.

I have looked and cannot find anywhere on how to change this listening port, Can anyone provide any insight on how to change this or is this not possible once you have finalised the server config, also as noted we restored a full backup and this clearly doesn't set the ports as you would expect, and another reason why this should have been noted in the upgrade.

I'm curious if anyone else encountered this issue, and if there is a reason this is not mention as part of the upgrade process, its seems like a core component of the upgrade and there should have been some note about it, Oddly can't seem to find anyone else that had this issue, several other post similar not quite the same issue.

I have 2 more clients to upgrade tonight so will see how that goes when I get to the port selection, hopefully as long as I set this my issues I had today will not be a problem for our other clients as there are about 50-70 users that are currently using PWA.

Thanks
Dan

 

[KyriacosS_3CX]

Hi,

During deployment/install you are asked if you wish to use the new ports or keep the old ones - and there is mention in the docs that you might need to edit the backup file if the upgrade includes a resore from backup.

 

[bitprecision]

I don't recall seeing this message as part of the deployment/install but I do know there was something I clicked though and kept the defaults, which may very well have been this screen.

I realise this is on me if I didn't pay attention to this, I guess as part of the checklist this is not mentioned so wasn't looking or expecting this to be a problem.

I have 2 sites to upgrade tonight, I'll be paying extra special attention to all the prompts I get,

Also our upgrade path is as follows

1. Full backup of v18 instance
2. Mount ISO to Vultr Instance (ISO is Debian 12 + 3CX v20)
3. Complete Deployment via Console
3. Restore Full backup Once 3CX has been deployed via WebUi provided in ISO deployment

 

[KyriacosS_3CX]

On debian you can for the most part do a "live" upgrade from within the admin console, that should keep all your settings etc intact.

Any reason you prefer the restore from backup (that you should of course be taking anyway)?

 

[bitprecision]

Yes, because the in-place upgrade fails. This is due to the server check, our clients are small, they don't need a 2GB 2CPU Core configuration, however it appears the in-place upgrade checks this and it fails if it doesn't meet 3CX "Recommended" Server config

So, we do it the way advised, we can't justify the additional cost for the server upgrade when we know it works perfect well with 1GB 1CPU Core.

If this restriction was not there then it should upgrade without having this issue and it would keep the current default listening port settings.

I don't understand why this doesn't appear to be configurable in the admin console though, it seems like something that should be there but for all the investigation I did today I was not able to see where this might be set

 

[KyriacosS_3CX]

The ports are locked in on installation, so yes it becomes critical to get that step right. You might need to edit the backup file as well to set the correct ports, but I believe you should be getting that screen shown above during the install prep.

I should note that v20 does need a bit more power than v18, so you might find that an upgrade of the VMs will be needed, and the support team might decline assistance when the hardware does not meet minimum requirements.

 

[bitprecision]

I can understand that, however support should not be denied if the server is not configured with the recommended requirements.

I'll make sure I check all the screens provided as part of the upgrade and hope this issue can be put to rest.

Appreciate your replies, ill post back here tomorrow, hopefully with some better upgrade results.

 

[bitprecision]

Successfully upgraded last night, Set the port and PWA is working without the need to reinstall the PWA app.

Thank you @KyriacosS_3CX your assistance was much appreciated.