FQDN issues??

[thereverendd]

My 3cx is not reachable by the FQDN but I can get to it directly by putting in the IP addressORT , The Dashboard
shows all the trunks are up but none of the extensions can reach the 3cx server. FQDN shows green on the INFO panel
but again can not be reached by typing the FQDN address. This is AWS hosted , Firewall shows GREEN , ran the test all good.
system extensions are green, services are green as well. Not sure what has happened here. I have restarted the AWS machine several times but no joy!

Really need to get this back up as soon as possible. Missing calls that are very important

Thanks in advance for any help

 

[SweetAction]

Is this a 3CX FQDN? If you do a lookup of the FQDN, does it resolve to the IP that the machine has currently? Has the IP changed recently?

You can try setting the IP to dynamic, wait a minute, set back to static if the machine has a static IP.

 

[thereverendd]

The system is not letting me change the IP on the screen its RED and says Dynamic right now. I do not see a way to change it to static. This is AWS so not sure they have static IPs

 

[Saqqara]

When you do an nslookup command, does the fqdn match the AWS wan ip address ?

 

[JohnS_3CX]

This should have already updated and it should have been working since you are in "dynamic" mode.

Are you perhaps using a PBX older than version V16.0.8.16?

If so, then there is nothing that can be done at this point because that system can no longer talk to our activation server to update its public IP.

You can only solve this by grabbing a backup and reinstalling using V18.

 

[thereverendd]

When you do an nslookup command, does the fqdn match the AWS wan ip address ?

It comes back with Can't Find : No answer

 

[thereverendd]

This should have already updated and it should have been working since you are in "dynamic" mode.

Are you perhaps using a PBX older than version V16.0.8.16?

If so, then there is nothing that can be done at this point because that system can no longer talk to our activation server to update its public IP.

You can only solve this by grabbing a backup and reinstalling using V18.

Oh,
Its 16.0.6.655 it wont allow me to do an UPDATE to the server it keeps failing as well any way to fix this so I do not have to reinstall the whole 3cx system?

 

[JohnS_3CX]

Yes, your current version is from almost 2 years ago. It can no longer reach the the old activation servers unfortunately because they were retired a couple of months ago. We sent out some emails but perhaps you missed them, no worries though because you can download a backup from your management console, and later re-deploy the system to get V18 + restoring your existing config so you don't lose anything.

You can also enable automatic updates if you wish, and the system will keep itself updated whenever we release a new stable version, which should prevent this from happening again in case the system has not been checked in a while by an admin.