So the DigitalOcean server that hosts my Discourse website had some type of issue and DigitalOcean is trying to migrate my website to another server. I am in contact with them about the issue but I wanted to see if anyone in the Discourse community has been through this issue before.
Does anybody have tips on this situation? Do they normally notify you when this process is complete? They haven’t responded to my e-mails yet. My website has been completely down for a couple of days and this isn’t good for my community. I didn’t make any changes to Discourse, so I know the problem occurred due to the DigitalOcean server issue. Is there anything specific I should do on my side, or should I just wait longer?
I turned the droplet off and on, as well as rebuilt Discourse with ./launcher rebuild app. After rebuilding I get this error:
Error response from daemon: driver failed programming external connectivity on endpoint app (fd1221330787160dee95f94a1256ca0dc8ddb8be2bc3c4d576ab54d3b768613a): Error starting userland proxy: listen tcp 0.0.0.0:80: bind: address already in use.
email from DigitalOcean:
We have identified an issue on the physical machine hosting one or more of your Droplets, which are listed below. In order to minimize disruption, we will be migrating the Droplets to a healthier physical machine. Throughout the migration, Control Panel and API events - including: power offs, resizes, and attempts to destroy the Droplet - will not succeed for the affected Droplet(s).
In order to minimize downtime, we will attempt to perform live migrations in all possible cases. A live migration would result in no downtime, but minor performance decreases in disk I/O and a second or less of packet loss as the network is switched over to the new physical host.
In the event that we are not able to perform a live migration of a Droplet, we will perform an offline migration during which the Droplet will be powered off and migrated offline during the window.