Before going into details, there are at least some questions that appear address the same problematic behavior, but the answers given to the questions do not apply in my situation, which I will explain. Here are the questions whose answers do not apply:
What is happening
I use Sequel Pro (1.1.2) from a new computer, Mac OS 10.14 (Mojave). I have tried to setup a MySQL connection via ssh on a server with which I work regularly, and the following error message is displayed:
Can not connect to HOSTNAME host because access has been denied.
Double check your username and password and make sure that access from your current location is allowed.
MySQL said: Access denied for the user USERNAME & # 39; @ & # 39; localhost & # 39; (using the password: YES)
As an added detail, I use SSL public authentication rather than password authentication.
What is not the problem
The answers to the questions I mentioned at the beginning do not apply because I always have the exactly the same The configuration of Sequel Pro works successfully on my old Mac (El Capitan, 10.11.4). In other words, it has nothing to do with the configuration of MySQL on the remote server, nor with the permissions granted to the user, nor with the specific configuration details that I provide to Sequel Pro, because I manage to connect to the same server with the same user on the old computer.
The only difference between the two configurations is that I use a new SSL key on the Mojave computer, a keyless key because Keychain no longer stores the secret phrases in the same way. I first tried using the original SSL key (with passphrase), which did not work … but for different reasons.
And yes, the new SSL key is working fine … I can very well connect to the destination server from the Mojave command line with the help of the new key.
In addition, I confirmed that the SSH connection to the remote server was not the problem in itself. I've replaced the "SSH User" field of Sequel Pro with a dummy user that does not exist and I have a different error. :
The SSH tunnel was unable to authenticate with the remote host. Please check your password and make sure you always have access.
This suggests that the problem comes from the MySQL connection once the tunnel established … but with the same configuration producing different results from different computers, it makes no sense that it is a problem on the server .
The problem lies therefore in the way the operating system allows Sequel Pro to create and use an SSH tunnel … is not it?
Why I'm stuck
I do not know how to find a solution to this problem, I do not know (with certainty) where to look to identify the problem.
- I can not figure out how to get a console log from Sequel Pro before the connection is established, to compare exactly what is going on behind the scenes on the respective computers. But as it is the same version of the software in both cases … it does not seem likely to me that this is where the divergence manifests itself
- I do not know enough about the SSH tunnel with enough confidence to manually recreate the situation without Sequel Pro.
- I am new for about 3 days at Mojave, and I do not know / still understand what could have changed between El Capitan and Mojave to introduce new variables
Real Sequel Pro error log on the new computer
… Pro Suite drives me crazy because only rarely provides a "Details" button in the failed login dialog. If I manage to get this option again, I will update this question with the log. Of course, if someone knows how to force Sequel Pro to display the details of the connection attempt and the subsequent error, please let me know and I will.
Any idea / help on this problem will be greatly appreciated.
Or, if there is another awesome and free MySQL client based on Mac that will successfully replace Sequel Pro, I'm open to suggestions …