Laravel; "SQLSTATE[HY000] [2002] Connection refused"

# Laravel: Decoding the "SQLSTATE[HY000] [2002] Connection refused" Error in Local Development As developers, setting up local environments—especially when dealing with virtual machines like Homestead—can often lead to frustrating connectivity issues. One of the most common hurdles encountered when integrating a Laravel application with a MySQL database is the cryptic error: `SQLSTATE[HY000] [2002] Connection refused`. This post will walk through the specific scenario you described, diagnose why this error occurs despite seemingly correct configurations, and provide actionable steps to resolve the connection refusal between your Laravel application and your MySQL server. ## The Paradox: Why Migrations Work But Data Fetching Fails You have correctly identified a paradox: data migrations succeed using Sequel Pro, but fetching live data from the running Laravel application fails with a `Connection refused` error. This strongly suggests that the issue is not necessarily with the database credentials themselves (username, password) but with the *network path* or the *service binding* being used by the two different applications. When you run migrations via Sequel Pro, you are likely interacting directly with the MySQL server process on a known port. When Laravel fails, it indicates that the PHP application context cannot establish an active TCP connection to the database host and port defined in its configuration. ## Analyzing the Configuration Conflict Let's review the settings you provided: **MySQL Configuration:** ```ini 'host' => '127.0.0.1' 'port' => '33060' ``` **Sequel Pro/Application Settings:** The configuration appears to be pointing toward `127.0.0.1` or `localhost`. In a standard VirtualBox/Homestead setup, the networking can sometimes introduce subtle differences between how the host OS (or GUI tools) resolve `localhost` and how an application running inside a VM resolves its network interfaces. The fact that changing from `'127.0.0.1'` to `'localhost'` did not fix the issue suggests the problem lies deeper within the networking layer managed by Homestead itself, rather than just a simple hostname resolution conflict. ## Deep Dive Diagnosis and Solutions The "Connection refused" error almost always points to one of three culprits: ### 1. MySQL Service Status (Most Common) The most immediate cause is that the MySQL service might not be running or might be listening on an unexpected interface within the VirtualBox environment. **Action:** Verify the status of the MySQL service *inside* your Homestead VM. Use standard Linux commands within the VM environment: ```bash sudo systemctl status mysql # Or, depending on your setup: sudo service mysql status ``` If the service is stopped or failed, starting it should resolve the issue immediately. ### 2. Port Binding and Firewall Issues Even if the service is running, a firewall (either within the VM or the host) might be blocking the connection on port `33060`. Additionally, ensure that the MySQL server is configured to listen on all interfaces, not just a specific internal IP. **Action:** Check if the MySQL process is actually bound to the network interface. Look at the MySQL configuration file (`my.cnf` or similar) and ensure settings allow external connections (though for local testing, this is less critical). If you suspect a firewall, temporarily disable it within the VM to test connectivity. ### 3. Laravel Configuration vs. Database Driver For complex setups involving custom ports, sometimes PHP's PDO driver needs explicit confirmation of the connection parameters. When dealing with database interactions in frameworks like **Laravel**, ensuring that your `.env` file correctly reflects the network setup is crucial for successful Eloquent