framework: "Whoops, looks like something went wrong." on brand new project

Laravel Version: 5.5
PHP Version: PHP 7.0.22-0ubuntu0.17.04.1

Description:

Updated laravel to 5.5 via composer global update. Created a new project using laravel new foo

Ran php artisan foo

Moving .env.example to .env and running php artisan key:generate makes the error go away.

And when creating a new project I see the following in my terminal:

Generating optimized autoload files
You made a reference to a non-existent script @php -r "file_exists('.env') || copy('.env.example', '.env');"
You made a reference to a non-existent script @php artisan key:generate
> Illuminate\Foundation\ComposerScripts::postAutoloadDump
You made a reference to a non-existent script @php artisan package:discover
Application ready! Build something amazing.

About this issue

Original URL
State: closed
Created 7 years ago
Reactions: 9
Comments: 20 (4 by maintainers)

Most upvoted comments

Hey @ikayyuddie try to find file .env in your project laravel. I have the same problem, thats the problem why its still doesn’t work. Because .env file just gone, i don’t know how it’s gone. you just copy .env file from another project, and change .env file as you need

+17

madun on Dec 4, 2017

I found running composer global update as solution for this issue, but actually running composer global self-update solved the issue for me

+10

samfrjn11 on Sep 18, 2017

rename .env.example as .env. Open it and update the data (especially Database config)

Azmeer-crescent on Feb 9, 2018

I had the same issue. I got the error because the missing .env file

ChristopherDosin on Feb 16, 2018

Browse the issues. Same question has been asked several times in the last 24 hours.

devcircus on Aug 31, 2017

This is because of your Laravel Installer or Composer version. I have faced the same problem and found following 2 different solutions:

Generally you can solve with by running composer global update command and then run composer update command from your project directory. This solution basically updates your installer and then your project.
If still, you have this issue, you need to run composer self-update command first and then run composer update command from your project directory. Here your composer will update and then your project.

Hope this answer will help you.

itskawsar on Oct 8, 2017

#20864 #20831 #20843

Looks like you just need to update your global composer dependencies so that laravel installer gets updated.

devcircus on Aug 31, 2017