HTTP 502 when connecting to sprite console

,
1

I’m getting an when I try to connect to a sprite.

$ sprite console
Error: failed to start sprite command: failed to connect: websocket: bad handshake (HTTP 502)

This only affects existing sprites; if I create a new one I can connect just fine. Any ideas what I’m doing wrong here?

3

I got the same thing. When I logged into sprites.dev I also notices all my existing sprites had vanished. All my checkpoints, everything, just gone it appears. I love the idea of sprites but building anything on them seems crazy given the lack of reliability. It’s kind of sad really.

4

Hi @superchris

I can see from our admin panel that you belong to 10 different organizations, perhaps you logged in into and org with no sprites?

You can try:

  • sprite org list to see which organizations you’re logged in
  • sprite org auth to auth to other organizatons
5

Hey @syvb can you send me which sprite name is currently behaving like that?

6

Well, this started because every time I tried to use one of my existing sprites I get a 502. I only have one org activated, and it show 0 sprites when I go to Sprites - Stateful sandboxes .

7

Same here. Existing sprite returns exact the same error:

❯ sprite s ls
Error: Failed to list sessions: API returned status 502:
❯ sprite exec -tty tmux
Error: failed to start sprite command: failed to connect: websocket: bad handshake (HTTP 502)

sprite ls
Sprites in organization dashan108-protonmail-com:

│shaolin-2│cold │5 days ago│

also, sprite-env service can’t start it.

Very unreliable solution yet.

8

Just chiming in to say I’m also experiencing the same issue.

9

Same lots of 502s!

10

Worked fine earlier today but for the past few hours, 502 is returned even though status is “Operational” (https://status.flyio.net):

Error: failed to start sprite command: failed to connect: websocket: bad handshake (HTTP 502)

11

Same. have a sprite that is 12 days cold. Cannot access via console. Upgraded CLI. Logged out / in. sprite ls shows my sprite.

Error: failed to start sprite command: failed to connect: websocket: bad handshake (HTTP 502)

Was working just fine last time I worked on it. Connect / disconnect for days during dev, no problems. Now I cannot connect. I want to work, cannot. Thinking of nuking it or spinning up a new one- but very nervous- too flaky to trust at this point.

12

Same, I 502 for every existing Sprite, even after logout.

13

Also getting

❯ sprite c
Error: failed to start sprite command: failed to connect: websocket: bad handshake (HTTP 502)

Happy to help debug if needed.

14

I guess there’s no way to create a new sprite using a checkpoint for the 502 sprite? :sad_but_relieved_face:

15

Not currently; that would be the much-requested copying/cloning/forking feature, which is still in the works last I heard:

https://community.fly.io/t/sprites-clone-sprite/26728/3

16

Well, my “broken” sprite went into “starting up” status after hours and I could log in again withou the 502 error. :sweat_smile:

17

As a small side note, the latest entry in the official Infra Log could shed some light on at least a few of the 5xx responses here…

https://fly.io/infra-log/wedged-sprites/

(It’s a good resource in general, for those who haven’t seen it before, :black_cat:.)