Laravel 5 2 not reading env file

Question

After upgrading to Laravel 5 2  none of my  env file values are being read  I followed the upgrade instructions  none of my config files were changed except auth php  They were all working fine in previous version  5 1 19   env contains values such as  DB DATABASE mydb DB USERNAME myuser   config database php contains   mysql    gt         database    gt  env  DB DATABASE    forge         username    gt  env  DB USERNAME    forge        I get this error   PDOException  SQLSTATE HY000   1045  Access denied for user  forge   localhost   using password  NO    Clearly not pulling in my env config  This is affecting every single one of my config files  including third party such as bugsnag   I also tried  php artisan config clear php artisan cache clear   Update  Trying php artisan tinker   gt  gt  gt  env  DB DATABASE     gt  null  gt  gt  gt  getenv  DB DATABASE     gt  false  gt  gt  gt  config  database connections mysql database     gt   forge   gt  gt  gt  dd   ENV       I have tried installing a fresh copy of Laravel 5 2  I basically only copied in my app folder  no additional composer packages are included  Still having the same issue  I have other Laravel 5 2 projects on the same server that are working fine

User · Answer

if you did call config cache during local development  you can undo this by deleting the bootstrap cache config php file  and this is work for me    Payal Pandav has given the comment above   I want to tell a simple workaround  Just edit the config php file in the bootstrap cache  folder  And change the credentials  This worked for me  Please don t delete this file since this may contain other crucial data in the production environment

User · Answer

I experienced this  Reason was that apache user www-data  could not read  env due to file permissions  So i changed the file permissions to ensure that the server  apache  had read permissions to the file  Just that and boom  it was all working now   Update How to do this varies  depending on who owns the  env file  but assuming it belongs to the Apache www-data group  you can do this   sudo chmod g r  env   Modify it depending on your permission structure

User · Answer

if you did call config cache during local development  you can undo this by deleting the bootstrap cache config php file  and this is work for me

User · Answer

Same thing happens when  port is in your local  env  again the double quotes does the trick  APP URL  http   localhost 8000    and then  php artisan config clear

User · Answer

In my case laravel 5 7  env  APP URL   not work but config  app url   works  If I add new variable to env and to config - it not works - but after php artisan config cache it start works

User · Answer

From the official Laravel 5 2 Upgrade Notes      If you are using the config cache command during deployment  you   must make sure that you are only calling the env function from within   your configuration files  and not from anywhere else in your   application       If you are calling env from within your application  it is strongly   recommended you add proper configuration values to your configuration   files and call env from that location instead  allowing you to convert   your env calls to config calls    Reference  https   laravel com docs 5 2 upgrade upgrade-5 2 0

User · Answer

For me the following worked  - php artisan config cache - php artisan config clear - php artisan cache clear

User · Answer

You can solve the problem by the following recommendation   Recommendation 1   You have to use the  env file through configuration files   that means you are requrested to read the  env file from configuration files  such as  config app php or  config database php    then you can use the configuration files from any location of your project   Recommendation 2    Set your env value within double quotation   GOOGLE CLIENT ID  887557629-9h6n4ne apps googleusercontent com   GOOGLE CLIENT SECRET  YT2ev2SpJt Pa3dit60iFJ   GOOGLE MAP  AIzaSyCK6RWwql0DucT7Sl43w9ma-k8qU    Recommendation 3  Maintain the following command sequence after changing any configuration or env value    composer dump-autoload  composer dump-autoload -o   php artisan clear-compiled  php artisan optimize   php artisan route clear  php artisan view clear   php artisan cache clear  php artisan config cache  php artisan config clear   Recommendation 4   When the syntax1 is not working then you can try another syntax2      val1   env  VARIABLE NAME           syntax1     val2   getenv  VARIABLE NAME        syntax2    echo  systax1 value is    val1    amp  systax2 value is    val2    Recommendation 5  When your number of users is high more then you have to increase the related memory size in the server configuration   Recommendation 6  Set a default probable value when you are reading  env variable      googleClinetId env  GOOGLE CLIENT ID   889159-9h6n95f1e apps googleusercontent com      googleSecretId env  GOOGLE CLIENT ID   YT2evBCt Pa3dit60iFJ      googleMap env  GOOGLE MAP   AIzaSyCK6RUl0T7Sl43w9ma-k8qU

User · Answer

I ran into this same problem on my local  and I have tried all the answers here but to no avail  Only this worked for me  php artisan config clear and restart server  Works like a charm

User · Answer

I missed this in the upgrade instructions      Add an env configuration option to your app php configuration file that looks like the following     env    gt  env  APP ENV    production     Adding this line got the local  env file to be read in correctly

User · Answer

I had a similar issue in my config services php and I solved using config clear and optimize commands   php artisan config clear php artisan optimize

User · Answer

delete cache using       php artisan config clear     php artisan config cache

User · Answer

When you fired command php artisan config cache then it will wipe out all the env variables and env   will give null values  try running following command and boom there your env   again begin to catch all env variable php artisan config clear

User · Answer

If you run this php artisan config cache command on console then it will store all the  env file contents in cache  after this command if you append any contents into  env file the it will not be not be available until you run php artisan config clear command

User · Answer

If any of your  env variables contains white space  make sure you wrap them in double-quotes  For example   SITE NAME  My website   Don t forget to clear your cache before testing   php artisan config cache php artisan config clear

User · Answer

Wow  Good grief  It s because I had an env value with a space in it  not surrounded by quotes  This   SITE NAME My website   Changed to this  SITE NAME  My website    Fixed it  I think this had to do with Laravel 5 2 now upgrading vlucas phpdotenv from 1 1 1 to 2 1 0

User · Answer

run this    php artisan config clear php artisan cache clear   then  php artisan config cache

User · Answer

For me it has worked this in this order   php artisan config cache php artisan config clear php artisan cache clear   And I ve tried all the rests without luck

User · Answer

I solved this problem generating a new key using the command  php artisan key generate

User · Answer

I had the same issue on local environment  I resolved by   php artisan config clear php artisan config cache and then cancelling php artisan serve command  and restart again

User · Answer

The simplicity is the power   php artisan config cache   You will receive   Configuration cache cleared   Configuration cached successfully

User · Answer

I face the same problem much time during larval development  some times env stop working and not return any value  that reason may be different that depends on your situation  but in my case a few days ago I just run     PHP artisan  config clear   so be careful use of this command  because it will wipe all config data form its cache  so after that  it will not return any value  So in this situation  you need to use this first if you have run  PHP artisan config   clear command   php artisan config cache     it will cache all data  php artisan config clear Configuration cache cleared

User · Answer

Tried almost all of the above  Ended up doing  chmod 666  env  which worked  This problem seems to keep cropping up on the app I inherited however  this most recent time was after adding a  env testing  Running Laravel 5 8

User · Answer

I had some problems with this  It seemed to be a file permission issue somewhere in the app - not the  env-file   I had to  - stop my docker  - use chown to set owning-rights to my own user for the whole project  - start docker again  This time it worked

User · Answer

Also additional to what  andrewtweber suggested make sure that you don t have spaces between the KEY  and the value unless it is between quotes   env file e g        SITE NAME  My website MAIL PORT  587 MAIL FROM NAME  websitename       to       SITE NAME  My website  MAIL PORT 587 MAIL FROM NAME websitename

User · Answer

I made the mistake by doing dd die dump in the index php file  This causes the system to not regenerate the configs   Just do dump in view files will do  The changes to  env file update instantly

User · Answer

Not sure whether is it already posted  but this combo worked for me  php artisan clear-compiled  composer dump-autoload php artisan optimize

[php] Laravel 5.2 not reading env file

Examples related to php

Examples related to laravel

Examples related to environment-variables

Examples related to laravel-5.2