Connection issues
Please answer the questions below, it helps us to keep track of the issue. Please do not ignore it or your issue will be closed.
-
Which driver are you using and version of it (Ex: PostgreSQL 10.0): MySQL 5.7
-
Which TablePlus build number are you using (the number on the welcome screen, Ex: build 81): 454
-
The steps to reproduce this issue: I'm connecting to a shared database @ Siteground. It's been fine for more than a year, and suddenly yesterday I started getting "Lost connection to MySQL server at 'waiting for initial communication packet', system error: 60" when connecting. If I delete the program (just the program) and reinstall it, then it connects perfectly the first time, but after that I get this error. It works fine connecting to Aurora MySQL @ AWS. Deleting the program and the data, then reinstalling, doesn't alter the problem. I've had Siteground check the firewalls, and there's no block. I've tried going in on alternate IPs (confirming remote access etc) and it makes no difference. From the same machine, I can connect using another MySQL client.
Noted: If the bug is related to data, please attach an example SQL data.
Hi @HassoEccard have you tried to restart macOS? I think there is an error in the macOS that blocks connections from TablePlus?
Thanks for the reply - it was the first thing I did, then again after various other changes. I'll look into anything 'inside' the mc that might be causing it.
I have had the same issue - it was caused by the AllowTcpForwarding option in /etc/ssh/sshd_config file on the server
I encountered the same problem. When I try to connect to the database using TablePlus, I get the error message: "Lost connection to MySQL server at 'handshake: reading initial communication packet', system error: 60." However, I can use other database connection software like Sequel Pro or Navicat without any issues.
Hi @BinaryAlan could you show me the connection config screenshot to [email protected] Thanks
Any update on this issue? A colleague of mine is getting this issue even though we have mimicked the exact setup and config on multiple other machines with no issues..