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?

1 Like
Unable to reach a sprite today
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!