warpdotdev
WPEngine SSH doesn't work in Warp
Discord username (optional)
No response
Operating System
MacOS
Operating System and Version
13.5.1
Local Shell Version
5.9
Remote Shell Version
5.1.16(1)-release
Warp Version
v0.2024.02.13.08.02.stable_00
I have tried commenting out my system & user rcfiles and warp still will not bootstrap
- [X] Yes
Screenshots
I'm trying to connect to WPEngine via SSH and kept getting errors no matter what I try. I finally tried in the Terminal app and it worked no problem. I tried commenting out my .zshrc file but I'm not sure what other rcfiles that can be causing this. It's not a super big deal, but just wanted to pass along the info.
Include shell xtrace output
bash: -c: line 1: syntax error near unexpected token then' bash: -c: line 1: export TERM_PROGRAM=WarpTerminal hook=$(printf {"hook": "SSH", "value": {"socket_path": "~/.ssh/170836946424693", "remote_shell": "%s"}} ${SHELL##*/} | command -p od -An -v -tx1 | command -p tr -d \n) printf %
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
I'm seeing this same behavior. Some additional context:
WP Engine uses a sandboxed SSH “sidecar” that sits alongside your server with a timeout of 10 minutes. Each site will have its own unique connection details and a separate sandbox to ensure there is no cross-contamination of sites or resources. This ensures the highest security level while allowing access to your site, without requiring additional steps such as IP allowing.
i see the same issue. mac terminal works fine, warp generates the error mentioned by op
Same for me on macOS 14.6, Warp v0.2024.08.27.08.02.stable_02
Works in default terminal and iTerm.
Seems related to https://github.com/warpdotdev/Warp/issues/3385
The workaround in that issue fixed it for me, i.e. turning off Warp SSH Wrapper in settings:
