Is the LHR region problem now in other regions?

My rails application stopped in DFW.
I did a new
$fly deploy

I am getting:
→ Build Summary: (​)
→ Building image done
image: registry.fly.io/jholist:deployment-01JPC7KB5KKNX3KX8TJBQXQ2JP
image size: 219 MB

Watch your deployment at Sign in to Your Account · Fly


Updating existing machines in ‘jholist’ with rolling strategy
Failed to update machines: failed to update machine e7843e43b60638: failed to update VM e7843e43b60638: request returned non-2xx status: 504: upstream request timeout Retrying…
Failed to update machines: failed to update machine e7843e43b60638: failed to update VM e7843e43b60638: request returned non-2xx status: 504: upstream request timeout Retrying…
Failed to update machines: failed to update machine e7843e43b60638: failed to update VM e7843e43b60638: request returned non-2xx status: 504: upstream request timeout Retrying…
Failed to update machines: failed to update machine e7843e43b60638: failed to update VM e7843e43b60638: request returned non-2xx status: 504: upstream request timeout Retrying…
Failed to update machines: failed to update machine e7843e43b60638: failed to update VM e7843e43b60638: request returned non-2xx status: 504: upstream request timeout Retrying…
Failed to update machines: failed to update machine e7843e43b60638: failed to update VM e7843e43b60638: request returned non-2xx status: 504: upstream request timeout Retrying…
Failed to update machines: failed to update machine e7843e43b60638: failed to update VM e7843e43b60638: request returned non-2xx status: 504: upstream request timeout


:check_mark: Cleared lease for e7843e43b60638

Error: failed to update machine e7843e43b60638: failed to update VM e7843e43b60638: request returned non-2xx status: 504: upstream request timeout (Request ID: 01JPC7R4ZBT4CWK5WMBKEW2N2B-dfw) (Trace ID: dd0558566ab0344c77c03229d2e397fb)

I can’t see anything here: https://status.flyio.net/

What’s in the response body of the 504?

Can you create a new machine/app in this region?

@halfer You asked what’s in the response body of the 504?

I think that was in the log that I printed in the original message.
e7843e43b60638: request returned non-2xx status: 504: upstream request timeout Retrying…

Failed to update machines: failed to update machine e7843e43b60638: failed to update VM e7843e43b60638: request returned non-2xx status: 504: upstream request timeout

I created a new machine/app in San Jose, California, and now everything is working correctly. Before my machine was in DFW (Dallas Fort Worth).

I still don’t know what caused my machine to stop working. It had been working for months. It was a rails 7.1.3.4 project running on ruby 3.2.2

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.