Lightsail Server died after reboot

Question

Rebooted my lightsail server last Friday. It never came back online. Status is "unknown" and public IP address is "unavailable". Stop, Manage, and Delete are the only options I have. History shows the server was stopped already. Opened a support ticket (on Friday) and was told there was a hardware failure. Support proceeded to ask me to try and stop/start via CLI. I get, "_Could not connect to the endpoint URL: "https://lightsail.us-east-2a.amazonaws.com/"_" when I run the stop or start commands. Support says they will escalate the issue. My server has been down for FOUR days now. Is there something I am missing here or could try?

Answer

Server is back online ... took amazon 5 days to get it back. Unacceptable. Will be rethinking if AWS is where I'll be staying.

Answer

psspro,  
  
Thank you for trying Lightsail and I hope you have been able to rectify your problem.  
  
Hardware failures are rare, but they do happen. In most cases, we can give prior warning to customers using the degraded hardware, but in some cases the failure does take an instance out without warning. In both cases the remedy is definitely to stop and then start the server (rebootInstance() will not work).  
  
One thing I noticed in your message is that the endpoint was listed as "https://lightsail.us-east-2a.amazonaws.com/". The "us-east-2a" part indicates to me that you used "us-east-2a" in your "--region" parameter to the CLI. "us-east-2a" is an availability zone whereas the region parameter needs a region name like "us-east-2". API endpoints for lightsail are all regional, so the domain name "lightsail.us-east-2a.amazonaws.com" simply does not exist.  
  
I hope this helps you.  
  
Donley

Lightsail Server died after reboot

Relevant content