Solved New 3CX deployment - DNS & Cert Issues Already

[gulf-pointe]

We've deployed a new cloud AWS server for 3CX and it's not even a few days old and having weird issues.

First - the Cert stops working randomly and we're not sure why

Your connection is not private​

Attackers might be trying to steal your information from xxxxxxxxxxxx.fl.3cx.us (for example, passwords, messages, or credit cards).

NET::ERR_CERT_COMMON_NAME_INVALID

The other issue is the the DNS resolution of the provided FQDN that is created. The AWS instance has a static IP publicly and has not changed once. The FQDN however changes to other IPs randomly so we drop all connectivity. We've gone through the admin settings and set it to Dynamic then back to Static as support requested but that is a band-aid - not a true fix.

Any help would be greatly appreciated.

Thanks - Anthony

 

[NikosT_3CX]

@gulf-pointe can you PM me the key that has this issue to check it ?

 

[NikosT_3CX]

@gulf-pointe as per our private conversation, there is no issue with your certificate or your PBX.
As we have discussed, the same key was attempted to be deployed again to AWS, this is why your IP address of the FQDN changed. Now it is reverted back to the correct one as the initial machine was still alive.

 

[gulf-pointe]

So we should be good now with the FQDN issue? i'll check further on the cert issue from here. please let me know.

 

[NikosT_3CX]

@gulf-pointe yes all are fine as per the screenshot I provided in your private chat, there is no issue at all from the PBX side and the certificate.