warpdotdev
FortiGate SSH Issue
Dupe Check
- [X] I have searched Warp bugs and there are no duplicates
Describe the bug
Unable to SSH onto FortiGate specifically with Warp.
To reproduce
SSH in every time, get disconnected.
Expected behavior
No response
Screenshots
Operating system
MacOS
Operating system and version
OSX
Shell Version
No response
Current Warp version
No response
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
No response
Additional context
No response
Does this block you from using Warp daily?
Yes, this issue prevents me from using Warp daily.
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:b9d78064-c89e-4973-b153-5178a31ee54e
None
Hi @ColvusBM sorry to hear about this. Warp has an SSH Wrapper that enables features (like the blocks, prompt, completions, etc.) on remote machines requiring the default prompt on the remote machine to be either bash or zsh.
As a workaround you can add command ssh to your Settings > Subshells > Added commands menu, then run command ssh <user@server> to connect to remote session, this will attempt to enable Warp features as a subshell.
You can also try disabling the SSH Wrapper by navigating to Settings > Features. Blocks will stop working but with it disabling, SSH should work as normal.
Related docs: https://docs.warp.dev/features/ssh https://docs.warp.dev/features/subshells
If those don't work, please let us know.
Good afternoon, The first option did the very same thing. The second option worked. Will this be fixed? RegardsBrandon. Sent from my iPhoneOn 22 Jun 2024, at 00:40, Danny Neira @.> wrote: Hi @ColvusBM sorry to hear about this. Warp has an SSH Wrapper that enables features (like the blocks, prompt, completions, etc.) on remote machines requiring the default prompt on the remote machine to be either bash or zsh. As a workaround you can add command ssh to your Settings > Subshells > Added commands menu, then run command ssh @.> to connect to remote session, this will attempt to enable Warp features as a subshell. You can also try disabling the SSH Wrapper by navigating to Settings > Features. Blocks will stop working but with it disabling, SSH should work as normal. Related docs: https://docs.warp.dev/features/ssh https://docs.warp.dev/features/subshells If those don't work, please let us know.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
Yes we plan to improve the SSh experience in an up coming cycle. We appreciate your patience as we work to make Warp better.
@ColvusBM - have you tried this recently, I work with many FG60 and FG100F and haven't had issues with the last few builds of WARP (both on linux and windows)
For me, the problem does show up on FG101F with latest FortiOS (v7.6.3) and Warp v0.2025.07.09.08.11.stable_01:
ssh fgcgn.misoft.lan
fortigatecologne # fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne #
command parse error before '$SHELL'
Command fail. Return code -61
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # > > > > > > > > > > >
command parse error before '-a'
Command fail. Return code -61
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Unknown action 0
fortigatecologne # Connection to fgcgn.misoft.lan closed.
