To allow remote access to MySQL on Mac, first, you need to modify the bind-address in the configuration file to 0.0.0.0 or a specific IP, and restart the MySQL service; second, create or modify user permissions, use 'remote_user'@'%' or specify the format of the IP and perform GRANT authorization; finally, check whether the Mac firewall releases port 3306 to ensure that the network connection is normal.
MySQL only allows local connections by default. If you run MySQL on your Mac and want to access it from a remote (such as connecting through another server or computer), you need to make some configuration tweaks. The core is to modify MySQL configuration files and set user permissions.

Modify MySQL configuration file to allow remote connections
The MySQL configuration file on Mac is generally located in /etc/my.cnf
or /usr/local/etc/my.cnf
. The specific path can be viewed through mysql --help | grep 'my.cnf'
.

Find a line like the following:
bind-address = 127.0.0.1
This means that MySQL listens only to local connections. You can comment out this line (prefixed with #
) or allow all IP connections instead:

bind-address = 0.0.0.0
This way MySQL will accept connection requests from any IP.
Note : If you just want a specific IP to connect, you can replace
0.0.0.0
as that IP address.
Restart MySQL after saving:
sudo mysql.server restart
Create or modify user permissions to allow remote access
By default, MySQL users may only be allowed to log in from localhost. You need to create a user for the remote connection or modify the permissions of the existing user.
Enter the MySQL command line:
mysql -u root -p
Then execute a command like the following to create a user that can connect from anywhere:
CREATE USER 'remote_user'@'%' IDENTIFIED BY 'your_password'; GRANT ALL PRIVILEGES ON your_database.* TO 'remote_user'@'%'; FLUSH PRIVILEGES;
-
'remote_user'@'%'
means that this user can log in from any IP. - If you only want to allow a specific IP, replace
%
with that IP, such as'remote_user'@'192.168.1.100'
. - The last sentence
FLUSH PRIVILEGES;
is to enable the permission change to take effect immediately.
Check firewall settings
Even if you have changed the MySQL configuration, if the system firewall blocks port 3306 (MySQL default port), the remote cannot be connected.
On your Mac, you can check that the firewall is on in System Settings → Privacy & Security and make sure that external connections are allowed to be made to port 3306.
If there is no graphical interface, you can use the command to view the firewall status:
sudo pfctl -s info
If the firewall is enabled, you may need to add rule to release port 3306.
Test remote connection
Try connecting from another machine:
mysql -h your_mac_ip -u remote_user -p
-
-h
is followed by your Mac's LAN IP or public IP. - If the connection is prompted, check:
- Is MySQL running
- Is the bind-address setting correct?
- Whether user permissions allow remote login
- Is the firewall open to port 3306?
Basically these are the operations. As long as the permissions, configuration and network are correct, the remote connection can be successful.
The above is the detailed content of how to allow remote connections to mysql on mac. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

GTID (Global Transaction Identifier) ??solves the complexity of replication and failover in MySQL databases by assigning a unique identity to each transaction. 1. It simplifies replication management, automatically handles log files and locations, allowing slave servers to request transactions based on the last executed GTID. 2. Ensure consistency across servers, ensure that each transaction is applied only once on each server, and avoid data inconsistency. 3. Improve troubleshooting efficiency. GTID includes server UUID and serial number, which is convenient for tracking transaction flow and accurately locate problems. These three core advantages make MySQL replication more robust and easy to manage, significantly improving system reliability and data integrity.

MySQL main library failover mainly includes four steps. 1. Fault detection: Regularly check the main library process, connection status and simple query to determine whether it is downtime, set up a retry mechanism to avoid misjudgment, and can use tools such as MHA, Orchestrator or Keepalived to assist in detection; 2. Select the new main library: select the most suitable slave library to replace it according to the data synchronization progress (Seconds_Behind_Master), binlog data integrity, network delay and load conditions, and perform data compensation or manual intervention if necessary; 3. Switch topology: Point other slave libraries to the new master library, execute RESETMASTER or enable GTID, update the VIP, DNS or proxy configuration to

The steps to connect to the MySQL database are as follows: 1. Use the basic command format mysql-u username-p-h host address to connect, enter the username and password to log in; 2. If you need to directly enter the specified database, you can add the database name after the command, such as mysql-uroot-pmyproject; 3. If the port is not the default 3306, you need to add the -P parameter to specify the port number, such as mysql-uroot-p-h192.168.1.100-P3307; In addition, if you encounter a password error, you can re-enter it. If the connection fails, check the network, firewall or permission settings. If the client is missing, you can install mysql-client on Linux through the package manager. Master these commands

InnoDB is MySQL's default storage engine because it outperforms other engines such as MyISAM in terms of reliability, concurrency performance and crash recovery. 1. It supports transaction processing, follows ACID principles, ensures data integrity, and is suitable for key data scenarios such as financial records or user accounts; 2. It adopts row-level locks instead of table-level locks to improve performance and throughput in high concurrent write environments; 3. It has a crash recovery mechanism and automatic repair function, and supports foreign key constraints to ensure data consistency and reference integrity, and prevent isolated records and data inconsistencies.

IndexesinMySQLimprovequeryspeedbyenablingfasterdataretrieval.1.Theyreducedatascanned,allowingMySQLtoquicklylocaterelevantrowsinWHEREorORDERBYclauses,especiallyimportantforlargeorfrequentlyqueriedtables.2.Theyspeedupjoinsandsorting,makingJOINoperation

MySQL's default transaction isolation level is RepeatableRead, which prevents dirty reads and non-repeatable reads through MVCC and gap locks, and avoids phantom reading in most cases; other major levels include read uncommitted (ReadUncommitted), allowing dirty reads but the fastest performance, 1. Read Committed (ReadCommitted) ensures that the submitted data is read but may encounter non-repeatable reads and phantom readings, 2. RepeatableRead default level ensures that multiple reads within the transaction are consistent, 3. Serialization (Serializable) the highest level, prevents other transactions from modifying data through locks, ensuring data integrity but sacrificing performance;

To add MySQL's bin directory to the system PATH, it needs to be configured according to the different operating systems. 1. Windows system: Find the bin folder in the MySQL installation directory (the default path is usually C:\ProgramFiles\MySQL\MySQLServerX.X\bin), right-click "This Computer" → "Properties" → "Advanced System Settings" → "Environment Variables", select Path in "System Variables" and edit it, add the MySQLbin path, save it and restart the command prompt and enter mysql--version verification; 2.macOS and Linux systems: Bash users edit ~/.bashrc or ~/.bash_

MySQL transactions follow ACID characteristics to ensure the reliability and consistency of database transactions. First, atomicity ensures that transactions are executed as an indivisible whole, either all succeed or all fail to roll back. For example, withdrawals and deposits must be completed or not occur at the same time in the transfer operation; second, consistency ensures that transactions transition the database from one valid state to another, and maintains the correct data logic through mechanisms such as constraints and triggers; third, isolation controls the visibility of multiple transactions when concurrent execution, prevents dirty reading, non-repeatable reading and fantasy reading. MySQL supports ReadUncommitted and ReadCommi.
