Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Whoops, looks like something went wrong. Laravel 5.0

Tags:

php

laravel-5

I installed Laravel 5.0 properly by cloning in git, and composer install, when I ran it to browser http://localhost/laravel/public/, it says

"Whoops, looks like something went wrong."

I did not make any changes after composer install.

Update after copy the env.example to .env this is result

RuntimeException in compiled.php line 5599: OpenSSL extension is required.

like image 427
jemz Avatar asked Mar 06 '15 06:03

jemz


People also ask

How to fix Whoops looks like something went wrong in Laravel?

Outdated composer If not, the app update might fail showing the error, “Whoops, looks like something went wrong.”. Solution : In such cases, we update the composer with the commands composer self-update or composer global update or composer update , depending on the kind of issue we're facing.

Why does whoops look like something went wrong?

Whoops, Something Went Wrong. Typically points to an issue with a stored cookie/token in your Chrome Browser. Try clearing your Chrome Browsers history/cache and logging back in.


1 Answers

The logs are located in storage directory. If you want laravel to display the error for you rather than the cryptic 'Whoops' message, copy the .env.example to .env and make sure APP_ENV=local is in there. It should then show you the detailed error messaging.

like image 137
kylehyde215 Avatar answered Oct 19 '22 22:10

kylehyde215