CODEWITHSUNDEEP
phplaravellaravel-5database-migrationhomestead
code-8
code-8

Reputation: 58810

Access denied for user 'homestead'@'localhost' (using password: YES)

I'm on a Mac OS Yosemite using Laravel 5.0.

While in my local environment, I run php artisan migrate I keep getting :

Access denied for user 'homestead'@'localhost' (using password: YES)

Configuration

Here is my .env

APP_ENV=local
APP_DEBUG=true
APP_KEY=*****

DB_HOST=localhost
DB_DATABASE=homestead
DB_USERNAME=homestead
DB_PASSWORD=secret

app\config\database.php

   'mysql'       => [
    'driver'      => 'mysql',
    'host'        => env('DB_HOST', 'localhost'),
    'database'    => env('DB_DATABASE', 'homestead'),
    'username'    => env('DB_USERNAME', 'homestead'),
    'password'    => env('DB_PASSWORD', 'secret'),
    'unix_socket' => '/tmp/mysql.sock',
    'charset'     => 'utf8',
    'collation'   => 'utf8_unicode_ci',
    'prefix'      => '',
    'strict'      => false,
    ]

How do I avoid this kind of error?

I've tried:

1

in app/database.php

Replace localhost with 127.0.0.1

'host'=> env('DB_HOST', 'localhost') -->'host' => env('DB_HOST', '127.0.0.1')

Also, in .env

DB_HOST=localhost --> DB_HOST=127.0.0.1

2

Try to specify the environment

php artisan migrate --env=local

3

Check to see if the MySQL is running by run

mysqladmin -u homestead -p status Enter password: secret

I got

Uptime: 21281 Threads: 3 Questions: 274 Slow queries: 0 Opens: 327 Flush tables: 1 Open tables: 80 Queries per second avg: 0.012

Which means it's running.

4

Check MySQL UNIX Socket (This step work for me)

Upvotes: 182

Views: 333161

Answers (30)

Hashim Aziz
Hashim Aziz

Reputation: 6165

If using Laravel Dusk with GitHub Actions

I ran into this issue trying to set up a CI/CD pipeline with Laravel Dusk, using the default GitHub Action workflow in the Dusk documentation, which - as I've come to except for anything related to Dusk - is lacking.

I fixed it by adding my database environment variables from my .env.dusk.testing file to the GitHub Actions workflow, to make sure that the GitHub Actions runner had access to them. I also optionally moved them from the "Run Dusk" step to the job-level, making them available to any other steps in the job:

name: CI

on: [push]

jobs:
  dusk-php:
    env:
      APP_URL: "http://127.0.0.1:8000"
      DB_DATABASE: CICD_test_db
      DB_USERNAME: root
      DB_PASSWORD: root
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - name: Prepare The Environment
        run: cp .env.example .env
      - name: Create Database
        run: |
          sudo systemctl start mysql
          mysql --user="root" --password="root" -e "CREATE DATABASE CICD_test_db character set UTF8mb4 collate utf8mb4_bin;"
      - name: Install Composer Dependencies
        run: composer install --no-progress --prefer-dist --optimize-autoloader
      - name: Generate Application Key
        run: php artisan key:generate
      - name: Upgrade Chrome Driver
        run: php artisan dusk:chrome-driver `/opt/google/chrome/chrome --version | cut -d " " -f3 | cut -d "." -f1`
      - name: Start Chrome Driver
        run: ./vendor/laravel/dusk/bin/chromedriver-linux &
      - name: Run Laravel Server
        run: php artisan serve --no-reload &
      - name: Run Dusk Tests
        run: php artisan dusk --env=testing -vvv
      - name: Upload Screenshots
        if: failure()
        uses: actions/upload-artifact@v2
        with:
          name: screenshots
          path: tests/Browser/screenshots
      - name: Upload Console Logs
        if: failure()
        uses: actions/upload-artifact@v2
        with:
          name: console
          path: tests/Browser/console

Upvotes: 0

muli
muli

Reputation: 47

in my case, i had not created the database by that name. Try changing the username, password and database name to suit what you have or visit :https://5balloons.info/fix-access-denied-for-user-homesteadlocalhost/

Upvotes: 0

Helper -Joe
Helper -Joe

Reputation: 101

A. After updating the .env file with database settings, clear laravel setting by "running php artisan config:clear"

B. Please make sure you restart your apache server / rerun the "php artisan serve" command for your settings to take effect.

Upvotes: 1

watkib
watkib

Reputation: 347

My app had been set up to use .env.local. I was checking .env the whole time.

Check that you are editing the correct .env file if you have several.

Upvotes: 0

Abdellah Ramadan
Abdellah Ramadan

Reputation: 365

From your question, it seems you are running homestead. In that case, make sure you're running the commands in your VM. Many devs including me often make mistake and run artisan commands outside of VM which the commands will try to connect to our local database accessible through localhost which is different from the database used by homestead. Cd to your Homestead directory and run

vagrant ssh

then cd into code if that is where you keep your projects and cd into your project and run php artisan migrate again I hope this will help other people.

Upvotes: 0

mh. bitarafan
mh. bitarafan

Reputation: 1076

in my case (laravel 5+) i had to wrap my password in single quotation marks and clear config cache:

DB_CONNECTION=mysql
DB_HOST=localhost
DB_PORT=3306
DB_DATABASE=database_name
DB_USERNAME=user_name
DB_PASSWORD='password'

and then run:

php artisan config:clear

Upvotes: 9

Picard
Picard

Reputation: 4112

In my case the error was "caused" by my Homestead / Vagrant configuration about which I forgot :) trying to run the migration just from command line.

In case of using Homestead Vagrant Box environment you should run your migration from within your Homestead machine (after connecting to it using ssh: [email protected]:22) then the access rights will be OK and will allow the migration to run.

Upvotes: 0

sradha
sradha

Reputation: 2244

just change these things in the .env file of your root folder.

DB_DATABASE=your_db_name
DB_USERNAME=your_db_user_name
DB_PASSWORD='your_db_password'

It worked for me.

Upvotes: 3

sh6210
sh6210

Reputation: 4540

in my case, after restarting my server the problem was gone.

exit/close the "php artisan serve" command and

re-run the command "php artisan serve" command.

Upvotes: 9

Apoorv
Apoorv

Reputation: 194

All you have to do is alter your .env file.

DB_HOST=localhost
DB_DATABASE=homestead
DB_USERNAME=homestead
DB_PASSWORD=secret

In front of DB_DATABASE, write the name of the database and in front of DB_USERNAME, use root.

Upvotes: 5

A1Gard
A1Gard

Reputation: 4168

after config db restart the:

 php artisan serve

If the serve is active before set db config.

Upvotes: 6

Abdou Tahiri
Abdou Tahiri

Reputation: 4408

The reason of Access denied for user ‘homestead’@’localhost’ laravel 5 error is caching-issue of the .env.php file cause Laravel 5 is using environment based configuration in your .env file.

1. Go to your application root directory and open .env file (In ubuntu may be it’s hidden so press ctrl+h to show hidden files & if you are in terminal then type : ls -a to show hidden files) in your editor and change database configuration setting. then save your .env file

DB_HOST=localhost
DB_DATABASE=laravelu
DB_USERNAME=root
DB_PASSWORD=''

2. then restart your apache server/web server. and refresh your page and you have done

3. If still issue try to run below command to clear the old configuration cache file.

php artisan config:clear

Now you are done with the error

Upvotes: 265

Ogbonna Vitalis
Ogbonna Vitalis

Reputation: 8248

Check your .env file, if you have edited any of the variables, kindly restart laravel server, and your problem will be solved

Upvotes: 1

Luis Lopez
Luis Lopez

Reputation: 571

After change .env with the new configuration, you have to stop the server and run it again (php artisan serve). Cause laravel gets the environment when it's initialized the server. If you don't restart, you will change the .env asking yourself why the changes aren't taking place!!

Upvotes: 5

Fred Ondieki
Fred Ondieki

Reputation: 2512

In Windows PC Follow below.

  1. Access the Root folder of your application.

  2. Edit the .env file

Access Root folder of your application

Edit the .env File

Edit the Highlighted and change the UserName and the password adn The database Name accordingly.

Upvotes: 9

Byron Wong
Byron Wong

Reputation: 155

If you have an error returning something like PDOException in Connector.php line 55: SQLSTATE[HY000] [1049] Unknown database 'laravelu' is due to you are changing your batabase config as DB_DATABASE=laravelu. So for now you either:

  1. Change the DB_DATABASE=[yourdatabase] or
  2. create a database called laravelu in your phpmyadmin

this should be able to solve it

Upvotes: 0

Connor Leech
Connor Leech

Reputation: 18873

I had the same issue using SQLite. My problem was that DB_DATABASE was pointing to the wrong file location.

Create the sqlite file with the touch command and output the file path using php artisan tinker. 

$ touch database/database.sqlite
$ php artisan tinker
Psy Shell v0.8.0 (PHP 5.6.27 — cli) by Justin Hileman
>>> database_path(‘database.sqlite’)
=> "/Users/connorleech/Projects/laravel-5-rest-api/database/database.sqlite"

Then output that exact path to the DB_DATABASE variable.

DB_CONNECTION=sqlite
DB_HOST=127.0.0.1
DB_PORT=3306
DB_DATABASE=/Users/connorleech/Projects/laravel-5-rest-api/database/database.sqlite
DB_USERNAME=homestead
DB_PASSWORD=secret

Without the correct path you will get the access denied error

Upvotes: 0

Vrushal Raut
Vrushal Raut

Reputation: 1228

If you are using the PHP's default web server (e.g. php artisan serve) you need to restart your server after changing your .env file values.

Upvotes: 21

Krishneil
Krishneil

Reputation: 1490

Sometime in the future. Try to clear your config first 

php artisan config:clear.

Close all the terminal /cmd windows and then restart terminal/CMD and this should get rid of the error message. See if it works.

Upvotes: 8

Muhammad Asad
Muhammad Asad

Reputation: 3803

TLDR: You need to stop the server Ctrl + c and start again using php artisan serve

Details:

If you are using Laravel, and have started local dev server already by php artisan serve

And after having above server already running, you change your database server related stuff in .env file. Like moving from MySQL to SQLite or something. You need to make sure that you stop above process i.e. Ctrcl C or anything which stop the process. And then restart Artisan Serve again i.e. y php artisan serve and refresh your browser and your issue related to database will be fixed. This is what worked for me for Laravel 5.3

Upvotes: 70

124697
124697

Reputation: 21901

I had the same issue and in the end It turned out that I just had to restart the server and start again

Ctrl + c then

php artisan serve

Upvotes: 12

DucaBgd
DucaBgd

Reputation: 276

i have find solution

  1. Go to your application root directory and open .env file (In ubuntu may be it’s hidden so press ctrl+h to show hidden files) in your editor and change database configuration setting. then save your .env file

  2. then restart your apache server/web server. and refresh your page and you have done

  3. If still issue try to run below command to clear the old configuration cache file.

This worked for me gl ...

Upvotes: 3

abSiddique
abSiddique

Reputation: 12343

Two way to solve it

First way (Not recommended)

Open your database config file (laravel_root/config/database.php) & search for the below code block.

        'host'      => env('DB_HOST', 'localhost'),
        'database'  => env('DB_DATABASE', 'blog'),
        'username'  => env('DB_USERNAME', 'root'),
        'password'  => env('DB_PASSWORD', ''),

Change the code block as below

        'host'      => 'yourHostName',
        'database'  => 'YourDatabastName',
        'username'  => 'YoutDatabaseUsername',
        'password'  => 'YourDatabasePassword',

Second way (Recommended by Laravel)

Check your Laravel root there have a file call .env if not exist, look for .env.example, copy/rename it as .env after that the file looks blow !

APP_ENV=local
APP_DEBUG=true
APP_KEY=someRandomNumber

DB_HOST=localhost
DB_DATABASE=homestead
DB_USERNAME=homestead
DB_PASSWORD=secret

CACHE_DRIVER=file
SESSION_DRIVER=file
QUEUE_DRIVER=sync

MAIL_DRIVER=smtp
MAIL_HOST=mailtrap.io
MAIL_PORT=2525
MAIL_USERNAME=null
MAIL_PASSWORD=null

Modify the below block as follow

DB_HOST=yourHostName
DB_DATABASE=yourDatabaseName
DB_USERNAME=yourDatabaseUsername
DB_PASSWORD=youPassword

Now it will work fine.

Upvotes: 34

Ferhat KOÇER
Ferhat KOÇER

Reputation: 4075

Check your ".env" file in the root folder. is it correct?

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

Upvotes: 3

wdog
wdog

Reputation: 621

if you are using php artisan migrate NOT from vagrant box but from host machine then you must define inside the .env the ip of the box 192.168.10.10

and obviously set permission to homestead user from your ip something like

grant all privileges on *.* to 'homestead'@% identified by 'secret';

in .env file 

DB_HOST=192.168.10.10
DB_DATABASE=homestead
DB_USERNAME=homestead

Upvotes: 23

Mike Wright
Mike Wright

Reputation: 111

Got it! Log in as root and grant homestead@localhost the rights to everything.

From your terminal:

$ homestead ssh

$ mysql -u root -p

Enter password: secret

mysql> grant all privileges on *.* to 'homestead'@'localhost' identified by 'secret';

Query OK, 0 rows affected (0.00 sec)
exit

Now homesteads regular user has access to all of your tables, and as such, should be able to run things like migrations.

Upvotes: 5

Jesus Gonzalez
Jesus Gonzalez

Reputation: 127

i using laravel 5.* i figure i have a file call .env in the root of the project that look something like this: 

APP_ENV=local
APP_DEBUG=true
APP_KEY=SomeRandomString

DB_HOST=localhost
DB_DATABASE=homestead
DB_USERNAME=homestead
DB_PASSWORD=secret

CACHE_DRIVER=file
SESSION_DRIVER=file
QUEUE_DRIVER=sync

MAIL_DRIVER=smtp
MAIL_HOST=mailtrap.io
MAIL_PORT=2525
MAIL_USERNAME=null
MAIL_PASSWORD=null
MAIL_ENCRYPTION=null

And that was over writing the bd configuration so you can wheather deleted those config vars so laravel take the configuration under /config or set up your configuration here.

I did the second and it works for me :)

Upvotes: 5

Eric Hepperle - CodeSlayer2010
Eric Hepperle - CodeSlayer2010

Reputation: 3918

I just wanted to post this because this issue frustrated me for about 3 hours today. I have not tried any of the methods listed in the other answers, though they all seem reasonable. In fact, I was just about to try going through each of the above proposed solutions, but somehow I got this stroke of inspiration. Here is what worked for me to get me back working -- YMMV:

1) Find your .env file. 2) Rename your .env file to something else. Laravel 5 must be using this file as an override for settings somewhere else in the framework. I renamed mine to .env.old 3) You may need to restart your web server, but I did not have to.

Good luck!

Upvotes: 4

code-8
code-8

Reputation: 58810

Check MySQL UNIX Socket

Find unix_socket location using MySQL

mysql -u homestead -p

mysql> show variables like '%sock%';
+-----------------------------------------+-----------------------------+
| Variable_name                           | Value                       |
+-----------------------------------------+-----------------------------+
| performance_schema_max_socket_classes   | 10                          |
| performance_schema_max_socket_instances | 322                         |
| socket                                  | /var/run/mysqld/mysqld.sock |
+-----------------------------------------+-----------------------------+
3 rows in set (0.00 sec)

Then I go to config/database.php

I update this line : 'unix_socket' => '/tmp/mysql.sock',

to : 'unix_socket' => '/var/run/mysqld/mysqld.sock',

That's it. It works for my as my 4th try.I hope these steps help someone. :D

Upvotes: 11

Sojan Jose
Sojan Jose

Reputation: 3238

When you install Homestead, this creates a default "homestead" database in the VM. You should SSH into the VM homestead ssh and run your migrations from there. If you are working locally with no VM, you'll need to create your database manually. By default, the database should be called homestead, the username is homestead and the password is secret.

check this thread on laracasts or this blog post for more details

if you are getting 

[PDOException] SQLSTATE[HY000] [2002] No such file or directory

try changing "host" in the /app/config/database.php file from "localhost" to "127.0.0.1" . you can find more details and other fixes here on this thread.

Also check whether you have specified the correct unix_socket . check this thread .

Upvotes: 11

Related Questions