search

subhra74 / snowflake

Graphical SFTP client and terminal emulator with helpful utilities
GNU General Public License v3.0
2.16k stars 231 forks source link

Unable to type in port number #81

Closed beto-p closed 4 years ago

beto-p commented 4 years ago

Linux or windows version, i can not type in the port number on go to next field without it defaulting to port 22, when most ssh connections use port 22 we use a 5 digit code for some of the servers.

I am able to use arrows up and down but takes a long time trying to reach port 56000.

Is this intentional or bug? would be great to just be able to type it in.

lusky3 commented 4 years ago

Just confirming that I can type in the port number on Windows (build 1903, 18362.592), both on v1.0.3 and v1.0.4.

beto-p commented 4 years ago

Video recording.zip

here is a video of how i cant and some how at the end i was able to change it and it changed after pressing tab which is the same key i pressed including the enter key and kept doing the same thing and it did not change.

using windows 10 1903 and also tested on ubuntu 19.04

vicdemuth commented 4 years ago

I have the same issue. On Linux, you can edit the saved config file directly to alter the port No. In my case there has been created a snowflake-ssh directory off my home when first run. The config file sits inside it as session store.json. Hope this helps until the devs can get to the bottom of it.

subhra74 commented 4 years ago

The issue has been fixed already, however the installers has not been released yet.

subhra74 commented 4 years ago

Linux or windows version, i can not type in the port number on go to next field without it defaulting to port 22, when most ssh connections use port 22 we use a 5 digit code for some of the servers.

I am able to use arrows up and down but takes a long time trying to reach port 56000.

Is this intentional or bug? would be great to just be able to type it in.

You can edit it, just type in the port number. however it wont allow higher than 32727 for now. (bug which is fixed but not deployed yet)

subhra74 commented 4 years ago

this issue is fixed in 1.0.4