DigitalOcean moved my droplet because of error on their end, broke my website and can't fix it now?

My website, which took me days to set up and deploy, had been working fine until I received this message from DigitalOcean

We’re scheduling to migrate your droplet on June 10, 2016 at 06:30 UTC.

Listed at the bottom of this email are your droplet(s) that will be a part of this maintenance.

Throughout a period of approximately 6 hours all the Droplets on the hypervisor where your Droplet resides will be migrated to a new host. We spread out the migrations to ensure that each of them run in a timely manner and completes successfully.

When your specific Droplet is queued for migration it will be powered off and you can expect about 1 minute of downtime per GB of your Droplet’s disk size.

We expect there to be very minimal downtime, however we do understand the time above may not be a convenient for you. If that is the case, you may open a support ticket and our support team can assist you in migrating to a new hypervisor ahead of time.

If you have any questions at all about please reach out to our team and we’ll be more than happy to assist you.

After they moved my droplet, my website was still down and I responded to the email multiple times asking why my website is down. I’ve been told now that my droplet is “up and running”, but my website is still down (502 Bad Gateway), and I have no way of fixing it or retrieving any of my old content.

What do I do now? I’m paying for a droplet that doesn’t work, I don’t know how to fix my website, and it’s all because my droplet was forcibly shut off, moved somewhere else, and turned back on with no regards for the content of my site. I’m confused, extremely disappointed, and feel helpless with no idea what to do now.

I’m asking the community now because the person responding to my emails hasn’t been answering the questions I’ve asked. Sorry for the trouble and I appreciate the help!

Show comments

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Hey there,

First off, I am very sorry a migrate caused issues for you. This is definitely not what we want to see happen.

This seems like an issue in your webserver’s configuration. The restart of it when your droplet was migrated caused this issue. You should check out your webserver’s logs for more info.

If you are still having problems, please open a support ticket and our team will be able to offer more real-time help on this issue.