FQDN updates - IP Change

[lmacvey62]

We are a long time self-hosted "free forever" 3CX installation and have always been running in the AWS cloud.
As part of our V20 upgrade we had to upgrade from a micro to small instance to meet the minimum spec requirements.

However, we lost the AWS assigned pool public IP address in the process and got assigned a new one from the AWS pool
https://tribuquent.my3cx.us is our FQDN
Pinging tribuquent.my3cx.us [52.33.84.204] with 32 bytes of data:
Ping statistics for 52.33.84.204:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss)

https://34.221.179.98/#/login
Customer service wants to send us to a support partner, which we never had from the beginning, to help with upgrade (but we already are done)
Further I doubt support partners have access to the DNS management of my3cx.us domain.

Of course now we can't login after the upgrade since our FQDN points to the wrong "A" record IP and V20 requires SSL


Has anyone experienced this and how did you get 3CX to update the "A" record on the my3cx.com domain?

 

[Charles_3CX]

The IP address assigned to your FQDN is the correct IP 52.33.84.204, but the 3cx system is not responding to this IP address or the FQDN.

You need to check the networking side of AWS and ensure that the ports are forwarded to the correct IP, you can also check under the admin console from this system, Advanced > network section, and ensure the correct internal and external Ip addressing is listed there.

 

[lmacvey62]

 

[lmacvey62]

The address is assigned from the AWS pool. This was due to the change from T3.micro to T3.small which created new network interface faces. No way to really go back at this point. I dont have the original IP address available in the elastic pool.

 

[Lee Cramman]

You usually do it by toggling between dynamic / static address in the admin console (although in V20 the web / admin console are the same).

I would ensure you login as system owner and see if that allows you to bypass the message.

If all else fails you could use the hosts file on a pc to ensure your fqdn points to your new IP. Once you can log in you can toggle to dynamic and then back to static to refresh the DNS entry, then remove the hosts file.

https://www.howtogeek.com/27350/beginner-geek-how-to-edit-your-hosts-file/

The hosts file entry would look something like:

tribuquent.my3cx.us 34.221.179.98

 

[lmacvey62]

I had not thought about using the host file to get around the https issue. Much appreciated and problem solved.