Solved After Cloud Computer instance restarted, Service Down.

[JustinCase]

I found out I had two ec-2 instances running on AWS (Amazon Web Services) so after bringing up a test call and stopping one instance, I was able to determine which one was carrying traffic so I terminated the one not needed. I must have started it while learning to build and launch a 3CX instance.
The issue is that after restarting the "good" one, it received a new DHCP address (52.x.x.x) according to the info I see when logged into AWS. It is different than what correlates to the IP assigned to the FQDN. I vaguely recall something in training that if you lose that IP for the FQDN, it's a difficult process to recover. I have the following concerns/questions:
1.) Symptoms are that I cannot get into the 3CX Mgt. Console neither by FQDN (Not found) so I had to use https://54.x.x.x/#/login (54.x.x.x = the new replacement IP).
2.) My 3CX PC client (Softphone) cannot register to the PBX
3.) Although this is a production environment, it's only me testing and learning, no paying traffic--but the system is down
4.) I can still resolve via nslookup my FQDN and it shows my old IP address that AWS provided
5.) When I log into the 3CX PBX via the new 52.x.x.x in the address bar, I still see my Public IP, the old one 54.x.x.x in the Dashboard on the right side pane under information and it's listed as Static, but AWS' DHCP must have given it a new one since I'm logged in via IP and now FQDN. I thought "PBX Express" (not sure what 3CX calls it now) worked with AWS to ensure a static IP?
6.) What is the best approach to restoring service?

 

[JustinCase]

Resolved. I didn't realize that the field showing the Static IP was a hyperlink. Upon clicking it, I was able to insert the new 52.x.x.x IP that AWS gave me after stopping and restarting the ec-2 instance (for those that aren't using AWS, that's just their term for one of many cloud-based computers).

Secondly, I had to restart the dozen or so 3CX services that were running so they could acquire the new IP address. After that, everything is back up.

Note: I chose to leave it as static IP in 3CX even though there is an option to select Dynamic which I unfortunately found out AWS doesn't give you as Static IP (I don't want to incur a month of basic support cost to ask AWS that question which falls under "technical."). For those that will be running their own PBX in the Cloud with AWS, I'd recommend setting it to Dynamic to avoid a situation like this after a Cloud PC restart.

 

[SweetAction]

Typically what you can do is set to dynamic and then back to static. That should trigger all the needed processes to update 3cx fqdn's, services, etc

 

[Alun]

I've just had exactly the same problem caused by exactly the same thing.

I followed the installation guide for AWS EC2, but instead of using the EC2 instance I'd just created, a second one was created in parallel. I only found out when Amazon sent me a bill for $1.93 for AWS-EC2 usage charges.

I went through the same "I'll stop one to see which is my 3CX server" thought process and got a new dynamic public IP.
Thanks for having this problem first!

 

[JustinCase]

SweetAction, thanks, that should help a lot of others looking to get their FQDN up with a new IP.

Alun, That's very interesting. I wonder if it's something that AWS has peculiar to the way the EC2 instance is created that causes that. The invoice from AWS for only $8.00 got my attention as to why...I should have contacted them when I saw two instances running but I didn't know any better. I thought it was something of their doing. Besides, my other $0.00 AWS Invoice was in EMEA for VAT and I'm only running in the US. Both instances were in US-east including the one I terminated.

Thanks for feedback, it's great.

 

[JohnS_3CX]

Keep it always on Dynamic, since what you have is a dynamic IP and may again change in the future.

 

[Alun]

My system has been back up and running since making the change to dynamic. I have one question about the UI though.

When I look at the dashboard for the admin account, my FQDN is show correct and below that is the IP address. it has been showing "detecting" in red since the change was made (3-4 days). Is that normal? Does it ever change to showing the current, dynamic IP address?

 

[JohnS_3CX]

Yeah, it should change after its been detecting for a short while.

You can restart your services (Management console/SIP Server) and it should go away.

 

[Alun]

Yeah, it should change after its been detecting for a short while.

You can restart your services (Management console/SIP Server) and it should go away.

That did it thanks!