Warp
Warp copied to clipboard
Can't connect to tmate session
Discord username (optional)
No response
Operating System
MacOS
Operating System and Version
13.3.1
Local Shell Version
5.9
Remote Shell Version
5.9
Warp Version
v0.2023.05.18.01.08.stable_04
I have tried commenting out my system & user rcfiles and warp still will not bootstrap
- [X] Yes
Screenshots
No response
Include shell xtrace output
There's not much on the output, but...
WARP_DEBUG_MODE=1 ssh [email protected]
Invalid command
Connection to nyc1.tmate.io closed.
Not sure how relevant it is, but it can be easily reproduced by installing tmate, and starting a new session on a new Warp tab (it works fine hosting the session!), then copying the ssh session (Warp fails with both the normal and readonly addresses), and trying to connect using a new Warp tab.
Connection will work normally by invoking a subshell and running ssh through it, though.
Does this block you from using Warp daily?
No
Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)
Yes, this I confirmed this only happens in Warp, not other terminals.
Warp Internal (ignore) - linear-label:e7dfaa84-5fdb-4a00-b754-d8912da923fa
None
Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e
None
Thanks for letting us know, @heyvito! We appreciate your feedback, and we'll make sure to post any updates regarding this issue on this thread.
Please add a 👍 to the original post at the top or comment with your details to signal that you're also experiencing the same issue. Additionally, feel free to hit the subscribe button if you'd like to be notified of any developments.
Meanwhile, you can disable the SSH Wrapper by navigating to Settings > Features. This will stop the Blocks functionality, but it should allow SSH to work as normal.
Hey @dannyneira! Thanks for the (super quick) reply!
I appreciate the directions to turn off the wrapper! Also please feel free to let me know in case I can provide any other information or be of assistance with anything else. :)
Cheers!
I experience this too, based on ssh wrapper: https://github.com/warpdotdev/Warp/issues/4630