No access to management console on cloud after change ip

[Raf]

Hi all,

I'm a first time user for both cloud and 3cx services.

Started on Google cloud services, moved via pbxexpress to AWS.

After migration everything worked perfect. Until I thought it was a good idea to move to a static public IP (read AWS elastic)
In console, it was set to use static ip (for one or another reason he didn't save the switch to use dynamic before I switched)
Didn't notice so I connected to elastic ip to my VM.

Restarted all the services on Debian Stretch, but afterwards I'm not available anymore to access the console via IP or FQDN.
nslookup of my fqdn (using 3cx fqdn), results into the previous IP, not the new one. (waited a couple of hours) but I assume that the public ip should be working.
(things have worked before so I'm assuming not AWS security policy)

Reinstalled from a backup with 3CXWizard --clean. Tried both options dynamic and static but still can't access the console.
IP mentioned during install is the correct public (new) IP

Services running :

$ ps -eaf | grep 3cx
phonesy+  1795     1  1 11:07 ?        00:00:00 /usr/lib/3cxpbx/CloudServicesWatcher -p /var/run/phonesystem/3CXEventNotificationManager.pid -c /var/lib/3cxpbx/Bin/CloudServicesWatcher.exe.config
phonesy+  1796     1  0 11:07 ?        00:00:00 /usr/sbin/3CXTunnel -n -p /var/run/phonesystem/3CXTunnel01.pid -c /var/lib/3cxpbx/Instance1/Bin/3CXPhoneSystem.ini
phonesy+  1797     1  0 11:07 ?        00:00:00 /usr/sbin/3CXMediaServer -n -p /var/run/phonesystem/3CXMediaServer.pid -c /var/lib/3cxpbx/Bin/3CXPhoneSystem.ini -m /var/lib/3cxpbx/Bin/3cxmediaserver.ini
phonesy+  1798     1  0 11:07 ?        00:00:00 /usr/sbin/3CXSLDBServ -n -p /var/run/phonesystem/3CXCfgServ01.pid -o /var/lib/3cxpbx/Instance1/Bin/Objects.cls -c /var/lib/3cxpbx/Instance1/Bin/3CXPhoneSystem.ini
phonesy+  1838     1  0 11:07 ?        00:00:00 /usr/sbin/3CXAudioProvider -n -p /var/run/phonesystem/3CXAudioProvider01.pid -c /var/lib/3cxpbx/Instance1/Bin/3CXPhoneSystem.ini
phonesy+  1839     1  3 11:07 ?        00:00:02 /usr/lib/3cxpbx/3cxSystemService -p /var/run/phonesystem/3CXSystemService01.pid /var/lib/3cxpbx/Instance1/Bin
phonesy+  1840     1  0 11:07 ?        00:00:00 /usr/sbin/3CXPhoneSystem -p /var/run/phonesystem/3CXPhoneSystem01.pid /var/lib/3cxpbx/Instance1/Bin/3CXPhoneSystem.ini
phonesy+  1842     1  4 11:07 ?        00:00:02 /usr/lib/3cxpbx/ManagementConsoleJS --pid /var/run/phonesystem/3CXPhoneSystemMC01.pid -p /var/lib/3cxpbx/Instance1/Data/Http/webroot
phonesy+  1869     1  1 11:07 ?        00:00:01 /usr/lib/3cxpbx/TcxQMsrv -p /var/run/phonesystem/3CXQueueManager01.pid /var/lib/3cxpbx/Instance1/Bin/config.json
phonesy+  1870     1  0 11:07 ?        00:00:00 /usr/sbin/3CXIVR -n -p /var/run/phonesystem/3CXIVR01.pid -c /var/lib/3cxpbx/Instance1/Bin/3CXPhoneSystem.ini

Nginx :

$ ps -eaf | grep nginx
root      1486     1  0 10:49 ?        00:00:00 nginx: master process /usr/sbin/nginx -g daemon on; master_process on;
www-data  1488  1486  0 10:49 ?        00:00:00 nginx: worker process

What am I missing?

Thanks to all
Raf

 

[YiannisH_3CX]

Hello @Raf

Even if the FQDN does not resolve to the correct IP you should be able to access the management console with your public IP and the correct port. If you are not able to do so make sure that you are using the correct IP and the correct https port.

 

[Raf]

HI @YiannisH_3CX,

thanks for the reply. Double checked the ip and port address but I was not able to connect.
Since today, my dnslookup seems to work and FQDN gives correct ip address. And now both ip and FQDN access seem to work correct.

Is it possible that the certificate caches some information got before a TLS 1 error.
Can I revert back from dynamic to static IP?

Kind regards

Raf

 

[JohnS_3CX]

Hi Raf,

Since the FQDN points at the right IP now and the console is accessible, you should be able to safely switch your PBX to static mode via the management console

 

[iaservers]

I have restored from https://pbxexpress.3cx.com/ a sesver (Google hosted) and now I have access to the new server, while both of them are online FQDN is the old one until the dns servers will be updated I guess, but I cannot manage the old server from google, I only see the new VM.

 

[JohnS_3CX]

The old server from Google - do you mean a free instance that 3CX provides for evaluation or an instance hosted on your own private Google Cloud account?

 

[iaservers]

It was the free instance, I had to contact support to erase it

 

[JohnS_3CX]

Yup, the old free version is not able to be managed by you because it was created under a 3CX google account. You can only manage the ones in your own Google account so contacting support was indeed the right move if you wanted to take it offline.