503 status code

Questions / Help
1

Hi Team,

I am getting the 503 status code for the deployed version. The health of an app looks good not sure why i’m getting 503.

I deployed on 2 different region.

  1. Toronto Canada- does not work
  2. Montreal Canada - works

Can anyone please help.

1 Like
2

Hey,

A few thoughts:

Do you see any issues/errors if you run fly logs?

Next try running fly status to see if there is at least one healthy vm running. Presumably that will be in Montreal right now.

And can’t hurt to take a look at the metrics (you can see the graphs on their dashboard). Do they show any spikes, out-of-memory issues, or anything like that?

1 Like
3

thanks for the reply…
I tried all seems healthy and its working now… not sure how but the instance is up and running

4

Hi Amigral,

Response status code 503 generally means the service is unavailable . This could mean that the server can’t handle the requests because of technical issues.

As Greg mentioned, it makes sense to run fly logs and, after that, fly status.
Sometime it helps fly to update itself, and it runs.

If you are able to share the logs, it will be much easier to find the issue.

5

Hi,

One of the reasons why an application returns error 503 is service unavailability, and this can be caused by several factors. Some likely causes:

  • Capacity issues or resources available on machines, such as CPU and memory.
  • Connectivity of your application in the Fly.io environment with external services, such as databases, APIs or queues
  • Incorrectly configured environment variables
  • Intermittent problems such as load spikes.

Therefore, analyzing the logs and viewing the current status of your machines using the fly logs and fly status commands can help you identify the real problem.

Here are two links that can help you identify these problems: