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
For the same mysql server, Sequel-Pro can connect but Sequel-Ace cannot #1944
Comments
I cannot understand it. If it is because of mysql server, but |
Moreover, I also have other msyql servers for 5.6.31 & 5.7.19, but both |
One thing to check - Sequel Pro uses your .ssh config, but Sequel Ace cannot automatically due to sandboxing. Try selecting your SSH config manually in Sequel Ace's network preferences. Perhaps you have some setting in there that is critical to connecting. |
Thanks for your reply. I tries to set the ssh config and known hosts, but it is still not ok. Moreover, I use |
This issue has been marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
I have the same problem. A mysql server via TCP/IP connect, can connected by Sequel Pro, but can not by Sequel Ace. |
For mysql |
Is Issue Present in Latest Beta?
I don't known.
Description
I had deployed two mysql servers on the remote host: 5.6.31 & 5.7.19.
I can use
Sequel-Pro
to connect to them, butSequel-Ace
cannot and reports the error as follow:Steps To Reproduce
Sequel-Pro
to access it with username and password.Sequel-Ace
to access it with username and password.Expected Behaviour
Sequel-Ace
can connect to the mysql server with the username and password.Related Issues
No.
Additional Context
No.
The text was updated successfully, but these errors were encountered: