Mosh users struggle to reach servers through SSH jump hosts
Developers using Mosh often need to reach servers through a bastion, but Mosh lacks an official ProxyJump workflow. The workaround described in the evidence involves a custom wrapper, UDP proxying, and bookkeeping; users also report trouble keeping SSH port forwards alive when Mosh takes over. Related reports point to a broader remote-session friction: disconnects can force re-authentication, and some remote developers rely on server-side tmux because they cannot install their preferred terminal there.
For developers using remote shells through bastion hosts. Mentioned from Oct 2012 to Jun 2022 on GitHub.
8 different people described this problem in 4 separate discussions.
- Indie fit
- 3.0/10
- Pain
- 6.0/10
- Frequency
- 7.9/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
I usually have to go through a proxy/bastion/jump server to get to my servers: ssh -J john@jumpbox john@myserver. Iis this not possible with mosh?
Implement ProxyJump > I think it'd be great if there were an official way to accomplish this. I've been getting around this with a wrapper by doing some UDP proxying, bookkeeping, and calling mosh-server and mosh-client directly: https://github.com/aduong/mosh-with-jump.
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 4 places to find your first customers
- 6 more quotes from people who have this problem
- Current workarounds, existing solutions and risks