4/10/2023 0 Comments Connect cleardb mysql sequel proMake sure you are both providing a password if needed and using the correct password for connecting from the host address you’re connecting from If the firewall is not the issue, then go over the list below and see if you have any of it:Ĭheck that MySQL is listening on port 3306 (note: 3306 is the default, but this can be changed)Ĭheck the user has rights to connect to the server IP from your address What you need to do is to check the firewall rules and see if it’s blocking any MySQL connection. There seems to be a problem with the firewall blocking outside connection. However, I gather that at least some people are successfully using Sequel Pro from Mojave, so that still leaves me stranded."Lost connection to MySQL server at 'reading initial communication packet, system error: 0" And according to Apple, that puts the onus on the vendor to update how the application code interfaces with the operating system and its new and more stringent policies. The only difference between the two is the version of operating system. (password is saved by keychain, and I have checked it 20+ times to make sure it's entered correctly in the Sequel Pro config screen) 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. This is my first attempt using a test build.I have tried setting the MySQL Host (in the Sequel Pro config window) to the hostname (yielding the info above), the public IP address (same problem), and 127.0.0.1 ("MySQL said: SSL connection error: Server doesn't support SSL").The settings in ~/.ssh/config that are applied are: ServerAliveInterval (250), ServerAliveCountMax (2), HostName, User, Port, IdentityFile.There is no passphrase required for the SSL SSH key.The exact same Sequel Pro configuration works on my old Mac, running El Capitan (OS 10.11.6).The remote server configuration (SSH, MySQL) is correct because I can connect using mysql-shell (command line) via the aforementioned SSH tunnel.My SSL authentication works because I can use it to manually create an SSH tunnel from the command line.(placeholders inserted for hostname/IP, username, etc) WHAT I ALREADY KNOW Here's what I get when I click "Show Detail": debug_details.txt MySQL said: Lost connection to MySQL server at 'reading initial communication packet', system error: 0 "SHOW DETAIL" You may also want to check the port is correct and that you have the necessary privileges.Ĭhecking the error detail will show the SSH debug log which may provide more details. Please ensure that your MySQL host is set up to allow TCP/IP connections (no -skip-networking) and is configured to allow connections from the host you are tunnelling via. Unable to connect to host HOSTNAME because the port connection via SSH was refused. I have tried to be as thorough as possible in providing details about the problem, the config details, etc., all provided below. I'm trying to connect to a remote MySQL database via SSH tunnel using SSL public/private key authentication.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |