Lost contact with my 3CX Console

[OpenedBy]

Hi guys,
A real noob question here sorry.
I created a 3CX instance on AWS and it was working except for PUSH notifications to 3CX apps. So, in an effort to troubleshoot the issue I created a local VM instance of 3CX and applied the key I was using in my AWS instance. This then seems to have updated the world wide DNS to point to our local IP instead of our AWS instance and now I can't get back to the AWS instance. Pinging our 3CX domain now points to our local IP instead of our AWS instance. How to I get the www DNS records to revert back to our AWS instance?

 

[Evolute IT]

Hi guys,
A real noob question here sorry.
I created a 3CX instance on AWS and it was working except for PUSH notifications to 3CX apps. So, in an effort to troubleshoot the issue I created a local VM instance of 3CX and applied the key I was using in my AWS instance. This then seems to have updated the world wide DNS to point to our local IP instead of our AWS instance and now I can't get back to the AWS instance. Pinging our 3CX domain now points to our local IP instead of our AWS instance. How to I get the www DNS records to revert back to our AWS instance?

First, turn off the local VM. Then, reboot the AWS one. You can connect to the console using the public IP of the AWS VM, then go to Settings --> Network and change the External IP Config to Dynamic (so the 3CX DNS updates).

After about 6h (Std, Pro) or 5min (Ent.), the DNS should be reverted back.

Please note that the License Key is bound to the FQDN of your instance for obvious reasons. You CANNOT have 2 running instances of 3CX with the same key, unless doing failover with an Enterprise license.

For your push notifications, for Android you can add your own Firebase API keys in Settings --> Phone/App Options. For iOS, make sure those ports are opened in your firewall as per https://www.3cx.com/docs/manual/firewall-router-configuration/ :

• Port 443 (outbound, TCP) for Google Android Push.
• Port 2195, 2196 (outbound, TCP) for Apple iOS Push.

 

[OpenedBy]

@Frederick Marcoux thanks for your response. DNSs have updated and I have our server contactable again. Valuable lesson learned thanks for the explanation.

Regarding the firewall config, yes I did read that documentation and I have an outbound rule in my AWS 3CX instance Protocol = All Port Range = All Destination = 0.0.0.0/0 which I thought would cover it. I will try having three explicit rules and see if that works.

Thanks again for your help.

 

[Evolute IT]

@Frederick Marcoux thanks for your response. DNSs have updated and I have our server contactable again. Valuable lesson learned thanks for the explanation.

Regarding the firewall config, yes I did read that documentation and I have an outbound rule in my AWS 3CX instance Protocol = All Port Range = All Destination = 0.0.0.0/0 which I thought would cover it. I will try having three explicit rules and see if that works.

Thanks again for your help.

make sure you're using the latest versions of 3CX and the mobile app.

 

[OpenedBy]

make sure you're using the latest versions of 3CX and the mobile app.

Yes to both those, 3CX v16.0.910
Android app 16.0.0.35

 

[OpenedBy]

I have a thread going on the Push issue here: https://www.3cx.com/community/threads/v16-0-910-push-not-working-on-any-phones-running-3cx-app.67039
And for completeness I should note the exact procedure I used to get the AWS instance back as the active instance.

1. Turned off the internal VM.
2. Restarted the AWS instance (didn't need to update the network settings, it reverted without that step.)
3. Within some minutes the global DNSs had updated.
4. Wiped sweat from brow