Database Laravel php artisan migrate connection refused

Question

When I use 'php artisan migrate' I get the following error message:

[Illuminate\Database\QueryException]
SQLSTATE[HY000] [2002] Connection refused (SQL: select * from information_schema.tables where table_schema = homestead and table_name = migrations)

[PDOException]
SQLSTATE[HY000] [2002] Connection refused

I've installed Laravel on a mac with XAMPP and have the following settings:

database.php

'mysql' => [
        'driver' => 'mysql',
        'host' => env('DB_HOST', 'localhost'),
        'port' => env('DB_PORT', '3306'),
        'database' => env('DB_DATABASE', 'forge'),
        'username' => env('DB_USERNAME', 'forge'),
        'password' => env('DB_PASSWORD', ''),
        'unix_socket' => env('DB_SOCKET', ''),
        'charset' => 'utf8mb4',
        'collation' => 'utf8mb4_unicode_ci',
        'prefix' => '',
        'strict' => true,
        'engine' => null,
    ],

.env

DB_CONNECTION=mysql
DB_HOST=127.0.0.1
DB_PORT=3306
DB_DATABASE=homestead
DB_USERNAME=homestead
DB_PASSWORD=secret

I've tried several solutions I could find online, but none have worked so far.

If you've installed with XAMPP, those are most likely not the correct database settings. You will have to figure out what those are and place them in your .env file. — user1669496
– user1669496, Commented May 5, 2017 at 12:30
I am using Mamp in Mac, I have same this issue. How can I resolved it? Thanks — huykon225
– huykon225, Commented Jan 28, 2018 at 9:25

Zoe - Save the data dump · Accepted Answer · 2019-05-11 14:47:59Z

34

This is really anoying, but changing DB_HOST=127.0.0.1 to DB_HOST=localhost solves the problem. Give it a try (obviously your file permission must be the right one)

edited May 11, 2019 at 14:47

Zoe - Save the data dump

28.4k22 gold badges130 silver badges163 bronze badges

answered Jul 18, 2017 at 12:54

Marcial Soto

4404 silver badges4 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Supun Abesekara Over a year ago

any idea about that??

Mark C. Over a year ago

Thanks Marcial! (This is a bit of an epic FAIL on the part of the laravel developers!!)

Jan Richter · Accepted Answer · 2020-03-23 08:54:16Z

8

If someone is experiencing this when using Docker, I had a multi-stage build with first container running the dependency installation and the second one just being the runtime. What I didn't realise is that the installation with Laravel scripts generate a cached config (bootstrap/cache/config.php) which is used instead of the config/database.php file.

Adding the following to the Dockerfile as the last step did the trick:

RUN php artisan config:clear

answered Mar 23, 2020 at 8:54

Jan Richter

2,0965 gold badges31 silver badges53 bronze badges

1 Comment

kregus Over a year ago

This also worked for me when using XAMPP VM version on MacOS. Thanks!

philyawj · Accepted Answer · 2019-02-24 18:10:33Z

7

The solution for me was different than anywhere else I found online.

I was unknowingly using the VM (virtual machine) version of XAMPP on Mac, which functions differently than the normal version. VM XAMPP interface looks like this.

If you are using the VM XAMPP, uninstall it and install the correct XAMPP version here.

Once I installed the new version php artisan migrate worked.

answered Feb 24, 2019 at 18:10

philyawj

1512 silver badges4 bronze badges

2 Comments

Ifadak Over a year ago

Thank you, I've tried several times but the error continues, not realizing that it's a virtual machine version.

Tandoh Anthony Nwi-Ackah Over a year ago

Great answer there .But can't something be done about XAMPP-VM for OS X to fix this issue with Laravel ?

crabbly · Accepted Answer · 2017-05-06 01:09:09Z

6

First create your database. Read more about it here: http://www.complete-concrete-concise.com/web-tools/creating-a-mysql-database-using-xampp

Let's say your new database is named: my_db.

Use this in your .env:

DB_CONNECTION=mysql
DB_HOST=127.0.0.1
DB_PORT=3306
DB_DATABASE=my_db
DB_USERNAME=root
DB_PASSWORD=""

answered May 6, 2017 at 1:09

crabbly

5,2261 gold badge26 silver badges48 bronze badges

Comments

Guy · Accepted Answer · 2019-07-10 13:19:47Z

2

I was using a Vagrant machine to run the whole thing, but I was mistakenly running command on my own machine.Thought this might help someone.

answered Jul 10, 2019 at 13:19

Guy

1,34218 silver badges19 bronze badges

Comments

Hareesh Sivasubramanian · Accepted Answer · 2018-05-26 13:23:08Z

0

Hi you don't have DB_SOCKET= /path/to/socket in env.file while you have unix_socket => env('DB_SOCKET', '') in database.php file.

You could get the /path/to/socket by $ mysql_config --socket

edited May 26, 2018 at 13:23

Hareesh Sivasubramanian

1,2607 gold badges17 silver badges28 bronze badges

answered May 26, 2018 at 7:15

YokoH

91 bronze badge

Comments

Saurabh Mistry · Accepted Answer · 2019-05-23 05:57:22Z

0

if you are using MAMP then in your .env file :

DB_HOST=localhost
DB_PORT=3306
DB_DATABASE=homestead
DB_USERNAME=root
DB_PASSWORD=root

answered May 23, 2019 at 5:57

Saurabh Mistry

13.8k5 gold badges60 silver badges78 bronze badges

Comments

Andris Briedis · Accepted Answer · 2022-09-03 09:51:52Z

0

I had a similar problem. Only it was using "ddev". It turned out that mysql responds to a completely different IP instead of 127.0.0.1 or locahost.

console: ddev ssh // If using ddev.
Login to mysql: mysql -y USERNAME -p
Runs this "SELECT SUBSTRING_INDEX(USER(), '@', -1) AS ip, @@hostname as hostname, @@port as port, DATABASE() as current_database;" It displays a table with data. The IP may not be the one to connect to. Must take is hostname.
ping "hostname" from the previous table. And then try to put the obtained IP in the .env file. Or "hostname". It also fits.

Now connection works.

answered Sep 3, 2022 at 9:51

Andris Briedis

4331 gold badge3 silver badges15 bronze badges

Comments

Victor Ighalo · Accepted Answer · 2019-01-15 07:08:05Z

-3

This is coming late but it might help someone. I had the same error, it turned out it was a typo in my .env file. Instead of DB_HOST, it was B_HOST. In your case it might be some other env key. Just look closer and you will discover the you have a malformed env file.

answered Jan 15, 2019 at 7:08

Victor Ighalo

1511 silver badge7 bronze badges

Collectives™ on Stack Overflow

Database Laravel php artisan migrate connection refused

9 Answers 9

2 Comments

1 Comment

2 Comments

Comments

Comments

Comments

Comments

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

9 Answers 9

2 Comments

1 Comment

2 Comments

Comments

Comments

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related