Code Robo
Java Code Complience
Virtual Service
upstream not found [519] error
       Talk to EasyAssistant

Upstream not found [519] error. Not able to connect AWS lightsail windows instance.

Its very frustrating and business loss. I was not able to connect AWS lightsail instance through RDP because of upstream not found [519] error. My site( was down for 2-3 hours. How i searching AWS documentation to figureout how the recover my data and make my site running. There are some steps given but it did not much help. Let me share my experience. I followed foloowing steps:
As not able to connect Lighsail instance. All operation tried from AWS console.
1. Create snapshot from the lightsail instance(Which is not reachable/broken ).
  • Stop Lightsail instance from AWS console
  • Created a snapshot (Lightsail > Snapshot > Manual snapshot > Create Snapshot ). It takes 10-15 mins to create the snapshot

2. Create new Lightsail instance from snapshot.
  • Select the snapshot (by clicking three vertical dots.)
  • Choose the option "Create new instance"
  • It will create a fresh instance. Instance was up and running.
  • But could not connect to this new instance as it did not generate the administrator password. It did not work for me. Later I found that it won't be working (password won't be generated) as snapshot was not taken/update through Sysrep procedure. To run the Sysrep procedure, we need to connect to the instance through RDP. But here main issue was not able to connect because of upstream not found error. This process will be helpful if you want to migrate from one instance to another instance(probably bigger) as that point of time you will able to process through Sysrep
Create Instance from snapshot

3. Export Snapshot To EC2 to recover the files through EC2 instance.
Create a snapshot of the "broken server" Export to Amazon EC2 (think of EC2 as a more manipulatable version of Lightsail) Create a new volume from that snapshot in EC2, and mount it on a new machine image
  • Select the snapshot (by clicking three vertical dots.)
  • Choose the option "Export to Amazon EC2"
  • Go to EC2 and Create a new volume from that snapshot in EC2.
  • Launch a fresh EC2 instance.
  • Attach the EBS volume to new instance
  • Mount it on a new image and access the files.
Export to Amazon EC2

4. Do multiple restart of your broFken server from AWS console. Hope for good luck. After 4-5 hours it may come up.

Do multiple restart and keep trying to connect. Hofefully you will be able to connect again after few hours.
It's painful, frustrating and loss of business loss

Post Your Comment:
Name :
Email ( Optional) :
Comments / Suggestion (* Required) It is required: :