“Whoops, looks like something went wrong.”
The Laravel application behind your site hit an error it couldn't handle. Because debug mode is off, as it should be on a live site, visitors get this one generic line instead of the details. The real error is written to the application's log, and that's where the fix starts.
Is your site showing it right now?
The free scan loads your page like a visitor and checks for this message, plus broken links, script errors and phone layout. It also walks your signup, booking or contact form, without sending anything.
Free, no signup. Usually done in about a minute.Why it happens
- A deploy that didn't finish: a missing dependency, a missing .env file, or an application key that isn't set
- The database is down, or the credentials in .env changed
- The storage or cache folder isn't writable, or a cached config still points at old paths
- A code change with a bug that only shows on the live server, for example a PHP version difference
How to fix it
Read the log
Open storage/logs/laravel.log on the server (or your error tracker). The last entry names the exception and the file and line that caused it, which usually points straight at the fix.
Don't turn debug mode on in production
APP_DEBUG=true shows the full stack trace to every visitor, including configuration values. If you need the trace, reproduce the error on a copy of the site, or read it from the log instead.
Check .env and clear the caches
Make sure .env exists with APP_KEY set and the right database details. Then run php artisan config:clear, php artisan cache:clear and php artisan view:clear so Laravel stops using cached settings from before the change.
Check permissions and dependencies
The storage/ and bootstrap/cache/ folders must be writable by the web server user. If the deploy skipped composer install, run it (composer install --no-dev).
Roll back if it started after a deploy
Put the previous release back so visitors have a working site, then fix the error in the new one and deploy again.
Questions
Why do I see the error but my developer doesn't?
Debug mode is usually on in development and off on the server, so they see the full error where you see the generic line. Send them the latest entry from storage/logs/laravel.log.
Is the site's data affected?
Usually not. The error stops a request before it finishes; the database is unchanged unless the log says otherwise.
Can Page Canary tell me if this comes back?
Yes. Page Canary checks your key pages every day for this message and others like it, confirms it on a second check, and emails you with the fix. One site is free.