Lightsail - Error We're having trouble displaying your resources

0

We have received an email telling us "Lightsail instance retirement scheduled" due to a degradation of the underlying hardware hosting one of your instances and that it will be stopped some time in the future. We would like to take a snapshot and manually stop and restart it before the planned maintenance but the Lightsail control panel does not show our instance or any of its snapshots. It shows this error

"Error We're having trouble displaying your resources - please try later"

We have tried later. This has been the same for over 3 days now. The instance is still running and we can reach the instance via ssh. How can we take a snapshot and stop and restart it?

asked 3 years ago585 views
5 Answers
0

Although a snapshot isn't a bad idea, it's not strictly needed in this case.

All you need to do is stop & start your instance and it will shift to different hardware.

Obviously that's the rub in your case.

Since you can SSH into the instance, try powering it off from the OS and power it back on from the lightsail control panel.

david

profile picture
David G
answered 3 years ago
0

Hi David,

Thank you for your reply. That is really helpful. In the mean time we have found that the Error we are getting back is unique to trying to interact with the AWS Lightsail console using Chrome browser ( on Mac Big Sur). We tried using Safari instead as a long shot and we can access the instance and take snapshots etc. fine. We will now stop and start it to clear the maintenance.

answered 3 years ago
0

Using Safari instead of Chrome (on Mac BigSur) removed the Error message and let us access the instance....

answered 3 years ago
0

Heh, I use Safari on my MBP and have never had a problem with the LS control panel. I've never tried Chrome or Firefox.

I just love the browser wars. <not/>

Glad you were able to resolve it.

profile picture
David G
answered 3 years ago
0

Iain Barclay,

Thanks for using Lightsail!

David is correct that stopping and starting the instance is sufficient to move it to a new, unaffected physical box. Note that OS-level shutdowns and reboots and the website's reboot function do not move the VM. Only start/stop will remedy the situation.

Regarding the issue of the error message you saw we are actively investigating this issue and will update this thread when it is resolved.

Thanks,

Donley

profile pictureAWS
answered 3 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions