![]() ![]() Here are the commands I'm using to successfully connect via command-line: ![]() I can connect fine from Sequel Pro on the old computer (using the same configuration) and from this computer when I manually create a tunnel and connect using mysql-shell. I don't understand how the problem could be with the MySQL side of things. So if you're getting it, then again it's not related in any type to the SSH/SSL. What further debugging/investigating happens now? (I believe 3 of those are default settings put in place by WHM/cPanel.) The user has "ALL PRIVILEGES" on 'localhost', on '127.0.0.1', on the hostname, and on the public IP address. ![]() I have confirmed that the MySQL user permissions are correct. MySQL said: Access denied for user (using password: YES) Unable to connect to host HOSTNAME because access was denied.ĭouble-check your username and password and ensure that access from your current location is permitted. This is the same error I was consistently receiving when using the public release of Sequel Pro 1.1.2 on the Mojave Mac. The problem now, if I uncheck the "Use SSL" box-regardless of what I put in the "MySQL Host" field-is that I get the following error message. Perhaps it was an incorrect configuration, but I went with what worked and therefore my inadvertent conflation of SSH and SSL continued.)Īs for the public IP vs 127.0.0.1, the public IP setting works fine on the old Mac. (As I mentioned in my original report, I used the exact same configuration in the last public release of Sequel Pro 1.1.2 on my other Mac, and it worked. I was using "SSL" incorrectly when I meant that I was using public/private key authentication via SSH. (I was hoping moving to Sequel Pro test builds would fix everything. I still successfully use the last official release, Sequel Pro 1.1.2, on the old Mac, but I have given up on 1.1.2 on Mojave due to operating system changes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |