massung

My feedback

  1. 7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    massung commented  · 

    Agreed. I currently have to use FileZilla for anonymous, public FTP access to transfer files, but would very much prefer to use Termius.

  2. 0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Desktop App » Windows  ·  Flag idea as inappropriate…  ·  Admin →
    massung commented  · 

    I discovered tabs can be renamed. I'm good.

    massung shared this idea  · 
  3. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Desktop App » Windows  ·  Flag idea as inappropriate…  ·  Admin →
    massung shared this idea  · 
  4. 35 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Implementing  ·  14 comments  ·  Desktop App » Windows  ·  Flag idea as inappropriate…  ·  Admin →
    massung commented  · 

    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.

    massung commented  · 

    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.

    massung supported this idea  · 
    massung commented  · 

    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.

Feedback and Knowledge Base