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?
Recommended threads
- Local appwrite run functions --user-id n...
Hi, I'm running into an issue when testing Appwrite functions locally with user impersonation. I'm using a self-hosted Appwrite instance and running functions ...
- Impossible to get USER after createEmail...
Am using provider to deal with functions linked to appwrite. Here is my login. Future<String?> login(String email, String password) async { try { aw...
- Selfhosted Github App installation
I've followed this guide: https://appwrite.io/docs/advanced/self-hosting/configuration/version-control to connect GitHub to my self-hosted Appwrite instance (1....