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?
TL;DR
Production server on data.limetrack.earth went down, restored a backup on data.lime-track.com, updated .env file, repointed DNS records, and got gateway timeout error on data.limetrack.earth. Issuing SSL certificates also failed. Need advice on resolving this urgently since customers cannot access the app.
Solution: Check SSL certificate issue and ensure it's properly configured for data.limetrack.earth. Also, verify DNS records and ensure they are pointing correctly to the server's IP address.
