Server Error on 3CX Management Console

[Rev E Miller]

Getting "Server Error" on 3CX Management Console when attempting to login since last night around 1:30AM Eastern Time.

 

[Rob Lifton]

Okay, I've restarted the VM Instance on Google and have now lost all access from Desktop phone and EVERYTHING, including no longer show the Management Console Login screen

Last night I started having the same "Server Error" issue. My VPS lives on a google cloud instance that I set up through 3CX as part of a free trial; it was set up giving 3CX access as it was being set up.

I just went in and restarted the instance and it gives me the error about the site not being reachable [MY FQDN] took too long to respond.

I would be interested in knowing how many others have been experiencing this issue.

-Rob

 

[Rev E Miller]

Rob Lifton, you basically just said what I should have said in the beginning. Great Summary!

 

[Rob Lifton]

Rob Lifton, you basically just said what I should have said in the beginning. Great Summary!

Another observation; it seems that restarting the instance has given me a new public IP address. When I go to that address https://xxx.xxx.xxx.xxx, I get a dire looking warning (the certificate must not have this new IP address). I am now able to log in, but not with my FQDN, as it has a DNS record to the old IP.

 

[Rev E Miller]

I just clicked on the "External IP" listed in the Instance information and after bypassing the 'Security Threat' Warning by clicking 'Advanced' and proceed anyways, it gave me the Management Console login screen. Now to see if I can 'reattach' the FQDN.

 

[Rob Lifton]

I was unable to do that, I released the FQDN and FQDN IP since they no longer worked. I do not see an option to re establish the FQDN association to my IP. I looked over the server info from the google cloud console and it had my public IP as XXX.XXX.XXX.XXX (ephemeral). So it looks like maybe it isn't a static IP? I suppose I'll need to reconfigure my phones. So we seem to have an issue that we don't know the cause of or if it will happen again. Next time it happens, do we need to restart the instance and lose the public IP thereby having to reconfigure the phones and SIP trunks?

 

[Rob Lifton]

I was able to change the IP from ephemeral to static from the Google Cloud console. Too bad there isn't an option to update the IP and FQDN from the 3CX customer portal. I guess I will have to use one of my domains to name the VPS so that I won't need to change EVERYTHING if/when this occurs again.

 

[Rev E Miller]

Well since I do a backup weekly, I'm trying to see if 'restore' might get me somewhere on the FQDN side and fingers crossed just updating the new 'IP' on the other side. We shall see.

 

[Rev E Miller]

I was able to change the IP from ephemeral to static from the Google Cloud console. Too bad there isn't an option to update the IP and FQDN from the 3CX customer portal. I guess I will have to use one of my domains to name the VPS so that I won't need to change EVERYTHING if/when this occurs again.

I was having difficulty with trying to change from Ephemeral to Static.

 

[Rob Lifton]

I was able to change the IP from ephemeral to static from the Google Cloud console. Too bad there isn't an option to update the IP and FQDN from the 3CX customer portal. I guess I will have to use one of my domains to name the VPS so that I won't need to change EVERYTHING if/when this occurs again.

Well, that's annoying - I created a DNS record with my domain registrar and changed my FQDN to that and some of it works (I can receive calls but not place calls). I had to go in and reconfigure my iOS softphone by hand and I can't see anything wrong, it just does not work.

 

[YiannisH_3CX]

In the management console please navigate to Settings / Network and check if the Option "External IP Configuration" is set to Static Public IP or Dynamic. If the PBX is set to Dynamic it will check for IP changes and will automatically update the DNS record to point your FQDN to the new IP. This is the case only if you are using a 3CX FQDN. ( If you are using your own FQDN and DNS then it is up to you to perform the change).
If the option is set to Static then the PBX will not check for IP changes. In the scenario that the PBX was set to Static and your public IP did change you need to set the option to Dynamic and restart 3CX services by navigating to dashboard / Services. Once the IP changes then you can set it back to static. Please note that the DNS records can take up to 6 hours to update depending on the licence you have.

 

[Rev E Miller]

not knowing what you now mention, I had to release FQDN from once 'free 3CX license and create a new one, because the Static/Dynamic IP changes were not implementing. Overall though, this specific issue is resolved. Just tightening up the settings on the new Instance to match the old Instance so that what was working works again. (and hopefully what wasn't fully functional will come in line).