I have client who I have hosted on AWS Lightsail. About 2 weeks after the initial install, they have been having an issue that shows at random times.
What i have observed is the FDNQ clientname.ga.3cx.us resolves to the incorrect IP address. I am using a static IP from AWS.
Observations when having the issues:
1.) If i ping the FDNQ it will respond with the same incorrect IP every time.
2.) If i navigate to https://wrong ip//#/login I do get a login page. (very freaking weird) and can login
3.) The above page does not have any of the clients configuration info. However, the "information" pane on the right has everything correct but the IP.
4.) If i navigate to https://correct ip//#/login I do get a login page and all the client configuration info is correct and present.
It would appear that the 3CX DNS servers are handing out a bad ip resolution.
What helps resolves the issues (not sure if it one thing or a combo)
1.) I restart the AWS instance
2.) I switch the external IP configuration (in network settings) from Static to dynamic (apply settings), then back again to static
I do have screen grabs so I am not completely off my rocker. I have several other instances on AWS with zero problems. But when this happens I have wait until the client lets me know then I am in a reactive mode. Does not make me or 3CX look good at the moment. Any Ideas folks??
What i have observed is the FDNQ clientname.ga.3cx.us resolves to the incorrect IP address. I am using a static IP from AWS.
Observations when having the issues:
1.) If i ping the FDNQ it will respond with the same incorrect IP every time.
2.) If i navigate to https://wrong ip//#/login I do get a login page. (very freaking weird) and can login
3.) The above page does not have any of the clients configuration info. However, the "information" pane on the right has everything correct but the IP.
4.) If i navigate to https://correct ip//#/login I do get a login page and all the client configuration info is correct and present.
It would appear that the 3CX DNS servers are handing out a bad ip resolution.
What helps resolves the issues (not sure if it one thing or a combo)
1.) I restart the AWS instance
2.) I switch the external IP configuration (in network settings) from Static to dynamic (apply settings), then back again to static
I do have screen grabs so I am not completely off my rocker. I have several other instances on AWS with zero problems. But when this happens I have wait until the client lets me know then I am in a reactive mode. Does not make me or 3CX look good at the moment. Any Ideas folks??
