search

vieten / sequel-pro

Automatically exported from code.google.com/p/sequel-pro
Other
0 stars 0 forks source link

SSH connection failed! #1077

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Using the config from version 0.9.8.1
2. Running it with 0.9.9, build 3327
3. produces: "SSH connection failed! - The SSH Tunnel has unexpectedly closed."
details:
"
OpenSSH_5.2p1, OpenSSL 0.9.8l 5 Nov 2009
Bad port ' -9223372036854775808'
"

It's working if I manually add the port 22 in the "SSH Port"-field.

Original issue reported on code.google.com by itsel...@gmail.com on 13 Jun 2011 at 6:41

GoogleCodeExporter commented 9 years ago 
Heh - thanks, it must not be getting picked up as blank correctly.  We'll 
address this.

Original comment by rowanb@gmail.com on 13 Jun 2011 at 9:18

GoogleCodeExporter commented 9 years ago 
Actually, quick though - what did it display in the "SSH Port" field?  Was it 
"optional", in grey, or a completely empty field?

Original comment by rowanb@gmail.com on 13 Jun 2011 at 11:23

GoogleCodeExporter commented 9 years ago 
It was "22" in grey.

Original comment by itsel...@gmail.com on 13 Jun 2011 at 11:24

GoogleCodeExporter commented 9 years ago 
Interesting - thanks for the update.

Original comment by rowanb@gmail.com on 13 Jun 2011 at 11:27

GoogleCodeExporter commented 9 years ago

Original comment by mattlangtree on 15 Mar 2012 at 10:58

GoogleCodeExporter commented 9 years ago 
Similar issue? Build 3734

OpenSSH_5.6p1, OpenSSL 0.9.8r 8 Feb 2011
debug1: Reading configuration data /Users/XXXX/.ssh/config
debug1: Applying options for XXXXX
debug1: Reading configuration data /etc/ssh_config
debug1: Applying options for *
debug1: auto-mux: Trying existing master
ControlPath too long

Original comment by silve...@gmail.com on 20 Jul 2012 at 1:30

GoogleCodeExporter commented 9 years ago 
silvexis,

I think your issue is a bit different; in the nightly builds we've switched to 
using a sandboxed temporary directory, which means the ControlPath can now be 
very long.  To address this I've switched to a short hashed marker for the 
controlpath file in r3781; we can't do anything about the folder path, but 
hopefully that addresses it...

Original comment by rowanb@gmail.com on 19 Aug 2012 at 9:15

GoogleCodeExporter commented 9 years ago 
This has only just started happenning to me after working fine with a greyed 
out port number right up until the 1.0.1 release (not sure on 1.0.0). Though I 
get no additional error, and the show details dialog is empty. Luckily the 
workaround of providing the port number works. I don't know if it's related to 
changing the SSH Port text to "optional" perhaps.

Original comment by george.g...@gmail.com on 31 Jan 2013 at 12:50

GoogleCodeExporter commented 9 years ago 
george - how baffling, thanks for the update.  Does the Show Details dialog not 
even contain a "Used command: ..." line?

Original comment by rowanb@gmail.com on 31 Jan 2013 at 12:57