Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'Bad local forwarding specification' under 10.11 and SSH tunneling #2164

Closed
alanhartless opened this issue Jul 4, 2015 · 12 comments
Closed

'Bad local forwarding specification' under 10.11 and SSH tunneling #2164

alanhartless opened this issue Jul 4, 2015 · 12 comments
Labels

Comments

@alanhartless
Copy link

@alanhartless alanhartless commented Jul 4, 2015

Love Sequel Pro (although would love a way to filter databases as servers with a large list of databases make it a bit tricky with a dropdown). :-) Any way off topic. Taking 10.11 El Capitan for a spin and now Sequel pro won't connect to any of my databases with SSH tunneling. It returns with the error like 'Bad local forwarding specification '61298/127.0.0.1/3306' Does the same under Sequel pro 1.1 RC. ssh -V outputs 'OpenSSH_6.7p1, LibreSSL 2.1.3'

Is there something I need to do Mac side to get it to work or is this a compatiblity issue?

Thanks!
Alan

@alanhartless
Copy link
Author

@alanhartless alanhartless commented Jul 4, 2015

Here's a masked version of the error details dialog:

Used command:  /usr/bin/ssh -v -N -o ControlMaster=no -o ExitOnForwardFailure=yes -o ConnectTimeout=10 -o NumberOfPasswordPrompts=3 -i /Users/myuser/.ssh/id_rsa.pub -o TCPKeepAlive=no -o ServerAliveInterval=60 -o ServerAliveCountMax=1 -p 22 user@server.com -L 61514/127.0.0.1/3306

Bad local forwarding specification ' 61514/127.0.0.1/3306'
@dmoagx
Copy link
Member

@dmoagx dmoagx commented Jul 4, 2015

Duplicate of #2050. This has been fixed in 1.1rc1 already.
Also you can filter databases in 1.1 via Database > Go to Database…

@dmoagx dmoagx closed this Jul 4, 2015
@dmoagx dmoagx added the Duplicate label Jul 4, 2015
@alanhartless
Copy link
Author

@alanhartless alanhartless commented Jul 4, 2015

Oops; sorry, I should have searched.

However, I had installed Sequel Pro from https://github.com/sequelpro/sequelpro/releases/download/release-1.1-rc1/sequel-pro-1.1-RC1.dmg and I'm still getting the error. Should I be using something else?

@alanhartless
Copy link
Author

@alanhartless alanhartless commented Jul 4, 2015

I apologize; something clicked and now it's working :-/ Not sure if I had an open instance of the old version or what. Thanks!

@rcdilorenzo
Copy link

@rcdilorenzo rcdilorenzo commented Aug 21, 2015

👍 I had this same problem and the 1.1-rc1 solved it.

@michaeldhopkins
Copy link

@michaeldhopkins michaeldhopkins commented Sep 24, 2015

👍 for the 1.1RC2. Thanks for the continued work on this!

@arezen
Copy link

@arezen arezen commented Oct 21, 2015

there is a bug with that versions, connections work, but there is an issue with BIT fields.
Bits does not show values accurately.

Waiting for 1.2

@kfsong
Copy link

@kfsong kfsong commented Dec 1, 2015

太赞了,1.1 RC1可以连

@grayghostvisuals
Copy link

@grayghostvisuals grayghostvisuals commented Mar 22, 2016

👍 💌

@vaibhav4git
Copy link

@vaibhav4git vaibhav4git commented Jun 7, 2016

Same issue faced, post helped ! Able to connect now.

@wenweih
Copy link

@wenweih wenweih commented Oct 11, 2016

update to latest version(1.1.2) work for me, thx.

@abcsun
Copy link

@abcsun abcsun commented Feb 28, 2017

It's work for me after updated to v1.1.2. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
10 participants
You can’t perform that action at this time.