1 Answer
- Newest
- Most votes
- Most comments
0
Hello,
Thank you for using Lightsail.
That message indicates that our web application has retried calls to the server and is unable to load data about your resources. Some of our team members have seen that when they enter a wifi dead zone and can't connect to the internet.
If this issue persists after you've ensured your network connection is stable, reach out to customer support. You can assist us in pinpointing this issue by providing them with a recording of the failing network calls (known as a HAR) and having it escalated to the Lightsail Frontend team. Do not post HAR files in a publicly accessible venue to avoid sharing personal data.
Here are the instructions for Chrome for your reference:
- Open Google Chrome and go to the page where the issue is occurring.
- Look for the Vertical ellipsis button ( ⋮ ) and select More Tools > Developer Tools.
- From the panel opened, select the Network tab.
- Look for a round Record button in the upper left corner of the tab, and make sure it is red. If it is grey, click it once to start recording.
- Check the box Preserve log.
- Click the round Clear button (on the right-hand-side of the Record button) to clear out any existing logs from the Network tab.
- Refresh the page to reproduce the issue that you were experiencing before. The network requests will be recorded as you reproduce the issue.
- Once you have reproduced the issue, in Chrome, click Download button (or right-click in one of the rows under the Name column under the Network tab, and then save the file to your computer: Save all as HAR with Content).
Regards,
Gabriel
Relevant content
- asked 4 years ago
- asked 2 years ago
AWS OFFICIALUpdated 3 months ago- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 3 months ago
Hello, thank you for your question. If you want to check if AWS Services are running healthy, you can always refer to the Service Health Dashboard: https://status.aws.amazon.com/ . You can also access a personalised version in your console, via https://phd.aws.amazon.com/phd/home , to understand what the impact - if any - there is on your resources.
With the information above, it's hard to reconstruct what could have gone wrong. Did you by any chance perform any actions on the server prior to noticing the failure?