`sftp shell` just not working

1

fly sftp shell -a <app> --machine <id>

just doesn’t connect :smile:

Here’s the agent logs:

2025/02/10 13:29:24.864882 srv OK 209354
2025/02/10 13:29:24.864982 #1 connected ...
2025/02/10 13:29:24.865036 #1 <- (   40) "set-token cfg /home/cole/.fly/config.yml"
2025/02/10 13:29:24.865102 srv (re-)connecting synthetics agent to https://flynthetics.fly.dev/ws
2025/02/10 13:29:24.865194 #1 -> (    4) "\x02\x00ok"
2025/02/10 13:29:24.865763 #1 <- (    4) "ping"
2025/02/10 13:29:24.865862 #1 -> (   57) "7\x00ok {\"PID\":209354,\"Version\":\"0.3.68\",\"Background\":true}\n"
2025/02/10 13:29:24.865893 #1 dropped.
2025/02/10 13:29:24.866395 #2 connected ...
2025/02/10 13:29:24.866436 #2 <- (   40) "set-token cfg /home/cole/.fly/config.yml"
2025/02/10 13:29:24.866562 #2 -> (    4) "\x02\x00ok"
2025/02/10 13:29:24.866588 #2 <- (   34) "establish redact-inc "
2025/02/10 13:29:24.866590 #2 establishing tunnel for redact-inc, 
2025/02/10 13:29:25.081234 srv returning port: 33947
2025/02/10 13:29:25.081252 srv (re-)connecting to wss://sea1.gateway.6pn.dev:443/
2025/02/10 13:29:25.106797 #2 -> (  775) "\x05\x03ok {\"WireGuardState\":{\"org\":\"redact-inc\",\"name\":\"interactive-redact-01JA9Z4MKEJHQ4W2G2SFT9HFWX\",\"region\":\"sea\",\"localPrivateKey\":\"[redacted]\",\"localpublic\":\"redactGulD8JhJA=\",\"dns\":\"\",\"peer\":{\"peerip\":\"fdaa:0:redactendpointip\":\"sea1.gateway.6pn.dev\",\"pubkey\":\"SN9V6BfrC9Dn+g84LGSDI+3VHBw3piOyaF2gZNuVNF4=\"}},\"TunnelConfig\":{\"LocalPrivateKey\":\"[redacted]\",\"LocalNetwork\":\"fdaa:0:4da4:a7b:177d:0:a:300/120\",\"RemotePublicKey\":\"redact=\",\"RemoteNetwork\":\"fdaa:0:4da4::/48\",\"Endpoint\":\"sea1.gateway.6pn.dev:51820\",\"DNS\":\"fdaa:0:4da4::3\",\"KeepAlive\":0,\"MTU\":0,\"LogLevel\":0}}\n"
2025/02/10 13:29:25.106846 #2 dropped.
2025/02/10 13:29:25.107716 #3 connected ...
2025/02/10 13:29:25.107770 #3 <- (   40) "set-token cfg /home/cole/.fly/config.yml"
2025/02/10 13:29:25.108053 #3 -> (    4) "\x02\x00ok"
2025/02/10 13:29:25.108104 #3 <- (   30) "probe redact-inc "
2025/02/10 13:29:25.108109 srv probing "redact-inc" ...
2025/02/10 13:29:25.132316 srv "redact-inc" probed: fdaa:0:4da4::3
2025/02/10 13:29:25.132354 #3 -> (    4) "\x02\x00ok"
2025/02/10 13:29:25.132370 #3 dropped.
2025/02/10 13:29:25.656817 #4 connected ...
2025/02/10 13:29:25.656872 #4 <- (   69) "connect redact-inc [fdaa:0:4da4:a7b:14:2ee8:83d:2]:22 0 "
2025/02/10 13:29:25.734145 #4 -> (    4) "\x02\x00ok"
2025/02/10 13:29:25.922618 srv synthetics agent connected to https://flynthetics.fly.dev/ws
2025/02/10 13:31:25.071256 srv redact-inc, map[redact-inc:0xc000727dd0]
2025/02/10 13:31:25.071273 srv validated wireguard peers
2

Hi,

Looks like they are on the case (certainly sounds like this is the cause):

3

That incident is resolved and sftp is still not working.

5

Hi :wave:, could you please try running another deploy for your app and see if this works? The incident was resolved because we rolled back the change we made to the deamon serving ssh, but it might still need a deploy for your app to pick it up.

6

Hello! I also have the same issue and I tried restarting the machine and also a redeploy. The sftp shell is still stuck with no output.

7

My colleague also confirmed it’s still not working. (We’ve redeployed the app in question multiple times today, including since 8 hours ago (the time of PeterCxy’s message).)

8

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