BUG: Port forwarding Not Working
I can't seem to locate a support contact, other than this suggestion. I am unable to get local port forwarding working with Termius on Windows. I have tried two machines both without success. I have tried opening the application with elevated privileges. However, the same issue persists. I can confirm that this is an issue with the application as PuTTY and X-Shell work perfectly fine with the same forwarding details. I have yet to try on my MacBook. However, this seems to be a bit of a deal breaker for me.
Any news on this? The documentation is very sketchy at best on this, something that takes seconds to fill out in other tools does not work here. It would be great if the documentation could give examples on how this is supposed to work - if it is supposed to work (which I assume, since the feature is available in the client).
I guess this issue is dead to the developers, no response for over 6 months. It's a shame, I'd totally use Termius as my preferred SSH client if this was working.
This functionality is not working on windows 10.
Got it working by swapping the logical ports for From and To, so the summary string seems to say the remote and local ports are the wrong way round but when I test then it works
To be a little more clear with my last comment...
Coming from Putty (and other SSH tools), I was under the impression that I had to "connect" to the actual site with a terminal window open and the port forwarding rule would be applied. After a little experimentation, I see that isn't the case.
Termius allows performing the Port Forwarding (via the "connect" action) without actually having a terminal window open to the site.
This is nice in some ways, but not so nice in others. For example, some of the servers I connect to have multiple ports that I want forwarded. With Putty, I simply connect to the server and all the ports are forwarded. While, with Termius, I have to "connect" many different rules. And, since I have dev/production servers with multiple ports, it means I can screw up by accident and potentially connect port A from dev and port B from production.
That's very nerve-wracking.
Following up for everyone here after working through this with support. The documentation isn't that great for port forwarding, but there's a single sentence at the very end that isn't very description but makes all the difference.
After you make the port forwarding rule, it's currently "disconnected" (a terrible adjective given that "connected/disconnected" has a very specific meaning for internet tools) from the host. Note to devs: a better adjective would be "unapplied" or "disabled". You need to "connect" it before it will become active.
To do this, just right-click the rule (or click the 3-dot menu icon) and choose "Connect". The port forwarding rule icon should change from gray to blue.
Once I did this, everything worked as expected for me.
I suggested to the support team - and am doing so here as well - that the UI show (in red) somewhere on the rule list that it is actually disabled and won't work until it is. I had no idea that the color of the icon had any meaning what-so-ever.
I hope this also helps someone else.
I have the exact same problem. This is the main reason I switched back to putty a while ago. Following this thread in case it gets fixed ...
Just adding that I cannot get it to work either... version 4.9.7 Windows. Works great in Putty. This (and agent forwarding) are the two features I need to work or the app is dead in the water to me. Really looking forward to being able to use Termius as my primary shell.
Could you try the latest 4.7.3 app version? Is the problem still there, please, contact our support: firstname.lastname@example.org
Please attach this information to your request:
1. The command which is working in your default system shell but is not working in Termius
2. The port forwarding rule screenshot which you are configured in the Termius
3. Any additional information which can help to reproduce the case
Note: if you wouldn't like your real data, you can just use some aliases works in the command and in the rule.
Same on macOS 10.14.5 and termius 4.5.0 on My iMac Pro
STILL NOT WORKING
Milan Muňko commented
Same on macOS 10.14.5 and termius 4.5.0
Jin Wang commented
It works before I upgrade to 4.5.0. Now it not woking for me.
Michael Gerndt commented
I do have the same problem on my MacBook Pro. Since I need forwarding to go to our Supercomputers, I can no longer use Termius on my Mac. On iOS it still works. It seems to me that the tunnel is created because I can use it from a normal shell. I cannot use from inside of Termius.
Yeah, I've confirmed that this is also an issue on Mac. Hopefully they'll fix it!
Alexandre Choisy commented
Same problem here on Mac. No way I can have port forwarding to work when a simple commande : ssh -L localPort:localhost:remotePort email@example.com work fine.
To bad but I ll have to stick to my console...
Any updates, or potential solutions to this?