503 errors
Your app may throw a 503 error and show Service Unavailable: No healthy endpoints to handle the request when you try to visit your URL. This means no healthy containers are currently available to serve your app.
Potential reasons for this include:
all containers are unhealthy, because they are all stuck in a CPU loop
no containers are running, because they are stopped or because every container crashed (especially if the total number of your containers is 1, and your app hasn’t had time to restart)
your build failed, if this is the first time you’re deploying a container for that app or if the only other available containers built successfully but are unhealthy
The most common cause of the 503 error is a problem in your code that prevents deployment - a deployment failure. Check the Logs tab to potentially find out more information about the issue.
A common reason that your app may be crashing on startup is that your MONGO_URL variable is missing or is set incorrectly. You can verify what MONGO_URL Galaxy is using by going to the app’s dashboard and choosing the settings tab. To learn how to set it correctly, check the following resources:
Environment variables will show you how to set up your settings.json file.
This compose.io article explains the settings for MONGO_URL and MONGO_OPLOG_URL in detail.
If you believe your MONGO_URL is set correctly, try the following:
Check the app dashboard and verify the app status is green (healthy).
Run `dig +show [your app's domain] `in the terminal and verify that its CNAME points to Galaxy. You can learn how to set up DNS here.
If you are in the US region, your CNAME should point to us-east-1.galaxy-ingress.meteor.com
If you are in the EU region, your CNAME should point to eu-west-1.galaxy-ingress.meteor.com
If you are in the Asia-Pacific region, your CNAME should point to ap-southeast-2.galaxy-ingress.meteor.com
If you recently changed your DNS settings, you may need to wait for the new records to propagate. DNS changes often propagate within 30 minutes (depending on the TTL configured for the record set), but in some cases it can take up to 24 hours. Contact your DNS provider if you think there is a problem.
Potential reasons for this include:
all containers are unhealthy, because they are all stuck in a CPU loop
no containers are running, because they are stopped or because every container crashed (especially if the total number of your containers is 1, and your app hasn’t had time to restart)
your build failed, if this is the first time you’re deploying a container for that app or if the only other available containers built successfully but are unhealthy
The most common cause of the 503 error is a problem in your code that prevents deployment - a deployment failure. Check the Logs tab to potentially find out more information about the issue.
A common reason that your app may be crashing on startup is that your MONGO_URL variable is missing or is set incorrectly. You can verify what MONGO_URL Galaxy is using by going to the app’s dashboard and choosing the settings tab. To learn how to set it correctly, check the following resources:
Environment variables will show you how to set up your settings.json file.
This compose.io article explains the settings for MONGO_URL and MONGO_OPLOG_URL in detail.
If you believe your MONGO_URL is set correctly, try the following:
Check the app dashboard and verify the app status is green (healthy).
Run `dig +show [your app's domain] `in the terminal and verify that its CNAME points to Galaxy. You can learn how to set up DNS here.
If you are in the US region, your CNAME should point to us-east-1.galaxy-ingress.meteor.com
If you are in the EU region, your CNAME should point to eu-west-1.galaxy-ingress.meteor.com
If you are in the Asia-Pacific region, your CNAME should point to ap-southeast-2.galaxy-ingress.meteor.com
If you recently changed your DNS settings, you may need to wait for the new records to propagate. DNS changes often propagate within 30 minutes (depending on the TTL configured for the record set), but in some cases it can take up to 24 hours. Contact your DNS provider if you think there is a problem.
Updated on: 01/07/2024
Thank you!