#Gateway timeout after migrating domain.

2 messages · Page 1 of 1 (latest)

azure musk
#

Late yesterday my production server on data.limetrack.earth went down. There are issues with my cloud service provider that I've been unable to resolve.

I restored the last SQL backup that I had from my production server onto my staging server, data.lime-track.com, and tested that I could see all of the data I expected to see. Everything works fine and all the data is there.

After updating my .env file to replace all occurances of data.lime-track.com with data.limetrack.earth, I repointed my DNS records so that data.limetrack.earth resolves to the same IP address as data.lime-track.com. I did this because I have a mobile app in production that accesses data.limetrack.earth. I allowed sufficient time for the DNS to replicate, brought all the containers online and then tested if I could access data.limetrack.earth. I get a gateway timeout error accessing the console.

I also received an email saying that issuing the SSL certificates failed (see next message). I believe that the two are likely related.

Does anyone have any advice/thoughts on how to resolve this, because my customers are currently not able to use my app?

#

I ran the following command sudo docker exec 0bcb5d89b4ee tail -300 /var/log/letsencrypt/letsencrypt.log to check what's going on with the worker-certificates container and this is what I see in the logs.