502 gateway errors on flyctl

I keep getting 502 gateway errors when using the fly CLI

Error create ssh certificate: server returned a non-200 status code: 502 (if you haven't created a key for your org yet, try `flyctl ssh establish`)
1 Like

it also happens to me during deployment using Github Actions, in the web interface an error message appears with the API and redirects to the login page, not to mention the delay to load the web interface

They seem to be investigating this now:

2 Likes

yesterday the same error happened (2022-08-28 18:30), but I saw that something related to a builder error and I recreated it 2 or 3 times, getting it working again

if you need I can provide the full build log of Github Actions to check the another timestamps

2022-08-29T16:54:49.3493431Z ##[group]Run flyctl deploy --remote-only
2022-08-29T16:54:49.3493837Z e[36;1mflyctl deploy --remote-onlye[0m
2022-08-29T16:54:49.3555645Z shell: /usr/bin/bash -e {0}
2022-08-29T16:54:49.3555980Z env:
2022-08-29T16:54:49.3556555Z   FLY_API_TOKEN: ***
2022-08-29T16:54:49.3556802Z ##[endgroup]
2022-08-29T16:54:49.7418184Z ==> Verifying app config
2022-08-29T16:54:49.7430156Z e[38;5;252m--> Verified app confige[0m
2022-08-29T16:54:49.7430774Z ==> Building image
2022-08-29T16:54:51.8523404Z Waiting for remote builder fly-builder-withered-sound-4526...
2022-08-29T16:55:21.5962564Z Error failed to fetch an image or build from source: error connecting to docker: failed building options: server returned a non-200 status code: 502
2022-08-29T16:55:21.5963158Z 
2022-08-29T16:55:21.5963222Z 
2022-08-29T16:55:21.5994027Z ##[error]Process completed with exit code 1.

Strange. Not sure what happened yesterday but today’s issue is now showing as resolved.

it is strange, but it only interfered with the deployment of a new version that failed, but the version that was already deployed was not interrupted

thanks for your attention and support

I was curious about a fact

Do 502s errors have something to do with Heroku announcing the end of free dynos and a mass migration of users to fly.io because it is one of the closest to it for simplicity?

@droposhado Ha, you are not the first person to ask.

But the answer is no :slight_smile: Guess it’s a nice problem for Fly to have though:

1 Like

I don’t know if it’s because of Heroku clients flowing in, but it’s been an absolute shitshow since I started on Fly. See my posts to see what I ran into in the last week or so…

I LOVE this service … if it works …

@Yaeger Ah. Yes, I see today has not gone particularly well :frowning:. Certainly seems to have been some influx.