Debugging

Below you will find common error scenarios and how to debug them.

502 Error when visiting your application

You will receive a 502 error when you application fails to startup. This is common for Docker container deployments, where your container builds successfully but fails on your run command.

The first step is to check your logs in the sherpa.sh portal. Visit the Logs page then select your project and deployment. Once you've selected the offending deployment in the tab filters in the upper right select "Application Console". Here you will see the most recent logs from your application - which likely will contain the source of the error.

To debug locally, please try building and running your docker container locally using this command:

docker build \
  --platform linux/amd64,linux/arm64 \
  --no-cache --pull --force-rm \
  --build-arg ENV_FILE=.env \
  --t local-test/my-project:latest \
  --load .

Make sure you have a .envfile in directory you run this command. This should contain the environment variables you have set for your application in the sherpa.sh dashboard.

Then running it using this command:

docker run --env-file .env local-test/my-project:latest

If you project runs locally this way, it should work on sherpa.sh and you'll stop experiencing the 502 error.

500 Error when visiting your application

This is likely due to a bug in your app, or a misconfigured environment variable. The first step is to check your logs in the sherpa.sh portal. Visit the Logs page then select your project and deployment. Once you've selected the offending deployment in the tab filters in the upper right select "Application Console". Here you will see the most recent logs from your application - which likely will contain the source of the error.