My VM is locked and my app stopped working and I can't deploy

Phoenix
,
1

I was getting 503s in my application on the day I launched on producthunt so I’m getting more traffic.

I was getting the following in the monitoring in the dashboard:
Could not proxy HTTP request. Retrying in 1000 ms (attempt 40)

Could not proxy HTTP request. Retrying in 1000 ms (attempt 50)

Could not proxy HTTP request. Retrying in 972 ms (attempt 60)

Could not proxy HTTP request. Retrying in 1000 ms (attempt 70)

Could not proxy HTTP request. Retrying in 1000 ms (attempt 80)

Could not proxy HTTP request. Retrying in 1000 ms (attempt 90)

could not find an instance to route to

So I tried scaling up the instance to 2GB (shared) and nothing is working. The status on each VM has been pending - I’ve tried stopping the VMs (works), trying to restart the VM (just hangs) and deploying also doesn’t work. When I deploy I get the following:

→ You can detach the terminal anytime without stopping the deployment
==> Release command detected: /app/bin/migrate

→ This release will not be available until the release command succeeds.
Error release command failed, deployment aborted

fly doctor also looks fine, everything passes.

Someone please help.

2

You could test if availability of your current location is the culprit by adding another location near you, set that as default and then try deploying again.

3

Update: It started working again when I kept deploying over and over… very annoying

4

Which app is this? The release command failure probably means an upstream database/service was not working properly. We won’t continue a deploy until the release command succeeds.

If this relies on postgres, it’s worth checking the status/health of the pg database.