Connect to the localhost using TCP

[yarkm13]

• Sequel Ace Version Version 4.0.13 Build 20062
• macOS Version: 14.2.1
• Processor Type: Apple M1 Pro
• MySQL Version: MySQL 8.0.35
• macOS Localization: uk

Description
I'm instructed to use host localhost and port 53322 but not a socket. As I know, 127.0.0.1 and localhost aren't the same from the MySQL GRANT permissions perspective.
Provided MySQL command is

mysql --user myuser --database mydatabase --port 53322 --host localhost --protocol TCP

But using host localhost it will try to connect using socket, even if TCP/IP tab is used. MySQL cli provides an --protocol TCP option to force the use of TCP/IP instead of a socket. It seems it's impossible to achieve that in Sequel Ace.

Steps To Reproduce

1. Configure MySQL server to listen on 127.0.0.1
2. Grant permissions to the myuser with the only host localhost
3. Use localhost as hostname in the Sequel Ace TCP/IP connection tab
4. Click "Test connection"
5. See the error "MySQL said: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)"

Expected Behaviour
I expect it will use TCP/IP host:port connection, because it's TCP/IP connection tab after all, and for socket connection, there is another tab.

Additional context
Why it's important for me now, it's because Teleport tunnel works that way. To securely use a remote database server and not introduce it to the world I need to use Teleport proxy. A command can be something like that:

tsh proxy db --db-user=myuser --tunnel --port 53322 db-service-name

and its result will be the following

Started authenticated tunnel for the MySQL database "db-service-name" in cluster "teleport.example.com" on 127.0.0.1:53322.

Use the following command to connect to the database or to the address above using other database GUI/CLI clients:
  $ mysql --user myuser --port 53322 --host localhost --protocol TCP

I believe it will be convenient to always use the TCP protocol while using the TCP/IP tab, which is expected, and get rid of that always annoying MySQL magic treating of localhost. And keep the socket tab for those who explicitly want to use sockets.

[Jason-Morcos]

I thought we fixed this ~3 years ago? #765
Not sure why we're having trouble here - the code should explicitly force localhost to be TCP/IP if you have TCP/IP selected
Can we get some screenshots of your connection configuration and the error message?

[yarkm13]

Maybe I'm reading this error message incorrectly?

[yarkm13]

There are different error messages for 127.0.0.1 and localhost

2024-01-22.11.30.05.mov

[Jason-Morcos]

It may be possible it's falling back on the socket if it cannot connect via TCP/IP?
Can you try with the correct password and see?

[Behinder]

Same problem here. I tried as 'root' and defined user - in terminal connection works in Sequel Ace it is not.

Standard connection, not the socket.

[AndrewLarsen]

Same here

When using the following command in terminal "mysql -uroot" it connects as expected.

But when I attempt to use Sequel Ace it doesn't work. It worked earlier today, but after I restarted mysql service (brew service restart mysql) it stopped working in Sequel Ace but not in terminal.

EDIT
For me this was related to "skip-name-resolve=ON" being enabled in my.cnf, localhost could not be resolved to 127.0.0.1, and when I attempted to use 127.0.0.1 I got an error message saying that the host 127.0.0.1 is not allowed.

Removed "skip-name-resolve=ON" and restarted mysql, and now localhost works as expected.

[Behinder]

Check if you have skip-networking option set on W dniu czw., 22.02.2024 o 09:26 Andrew Larsen ***@***.***> napisał(a):

…

Same here When using the following command in terminal: mysql -uroot It connects as expected, but when I attempt to use Sequel Ace it doesn't work. Weird is that it worked earlier today, after I restarted mysql service (brew service restart mysql) it stopped working in Sequel Ace but not in terminal. Screenshot.2024-02-22.at.09.25.10.png (view on web) <https://github.com/Sequel-Ace/Sequel-Ace/assets/7068614/93fbdb88-0e66-4d35-af45-d9bdff0b7f39> — Reply to this email directly, view it on GitHub <#1958 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEQPFSS5OFF3WV4VKQ7GR3YU36MBAVCNFSM6AAAAABCEB2FLSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJYHEZTMNBYGQ> . You are receiving this because you commented.Message ID: ***@***.***>