search

ipvisor / sshtunnel

Automatically exported from code.google.com/p/sshtunnel
GNU General Public License v3.0
0 stars 0 forks source link

Error: cannot connect to the host #187

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Tunnel Switch Enable/Disable SSH Tunnel
2. Error: cannot connect to the host

What is the expected output? What do you see instead?
Expected connection to the SSH host, instead there is no connection

What version of the product are you using? On what operating system?
SSHTunnel 1.5.6 on Samsung Galaxy S5, Android 4.4.2.

Please provide any additional information below.
I am able to authenticate with a key in ConnectBot (same host and port 
setting). So I copied the private key to a file called /sdcard/sshtunnel/key. 
This still did not allow a connection to my SSH server. The logcat data 
(filtered with SSHTunnel) is attached. The only setting I'm really unsure of is 
the "Local Port" setting of 1984.

Original issue reported on code.google.com by brianbga...@gmail.com on 9 Jul 2014 at 3:15

Attachments:

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Ok, more info. I was able to go onto my own network and set the host to my 
internal server address, ALSO, I set the port to 22. I was able to connect to 
the host but had to use password authentication. Now get this... when I put in 
my dns name in the host field, and changed the port to my external SSH port 
(not 22!!!) I could not connect, even within my own network.

So, there is definetly a bug. I'm wondering if possibly this app doesn't work 
with any other port than 22. Every example I've seen on the web shows the users 
entering port 22 as the host port. Hopefully this issues forum is still being 
monitored because it looks like SSHTunnel will do exactly what I want!!!

Original comment by brianbga...@gmail.com on 9 Jul 2014 at 5:35

GoogleCodeExporter commented 8 years ago 
Update: I'm able to connect... there was a space after my host name. After 
removing the space, it worked with password authentication. But, it still isn't 
working with the private key. If anyone has an idea on how to confirm the key, 
I'd appreciate it!

Original comment by brianbga...@gmail.com on 10 Jul 2014 at 2:04