The Laravel Errors I Fix Most Often (and the Fastest Fix for Each)

Most Laravel errors I deal with aren't new. They're the same ones I've already fixed, coming back on a fresh server, a new project, or a teammate's machine. The annoying part isn't fixing them. It's spending twenty minutes figuring out which one it is this time.

So I wrote this cheat-sheet for myself. I'm Yudhi, a web developer from Indonesia, and I work in Laravel most days. Each entry has the error message, what's actually causing it, and the fix I try first. Everything here applies to Laravel 10 and 11.

1. 419 Page Expired

419 | PAGE EXPIRED

Cause: The CSRF token was missing, didn't match, or the session it belonged to has expired. Laravel is rejecting the request on purpose. This isn't a bug in your code.

Fix: Put the token in every form:

<form method="POST" action="/profile">
    @csrf
    ...
</form>

For AJAX, add the token to a meta tag and send it as a header:

<meta name="csrf-token" content="{{ csrf_token() }}">

fetch('/profile', {
  method: 'POST',
  headers: { 'X-CSRF-TOKEN': document.querySelector('meta[name="csrf-token"]').content },
});

If it only happens on production, check SESSION_DOMAIN and SESSION_SECURE_COOKIE in .env. A cookie that never gets saved looks exactly like an expired token.

2. 500 Internal Server Error (blank page, no details)

500 | SERVER ERROR

Cause: It could be almost anything. The 500 page is just Laravel hiding the real exception from your visitors, which is what you want in production.

Fix: Don't guess. Read the log:

tail -n 50 storage/logs/laravel.log

If nothing is being logged, the problem is usually that Laravel can't write the log file at all (see #7) or that APP_KEY is missing:

php artisan key:generate

Only turn on APP_DEBUG=true for a minute while you're watching, then turn it off again. Debug pages show your environment variables to anyone who loads them.

3. Vite manifest not found

Vite manifest not found at: /var/www/app/public/build/manifest.json

Cause: Your Blade layout calls @vite(...), but the frontend assets were never built, or the build output wasn't deployed.

Fix: For local work, keep the dev server running:

npm run dev

For production, build the assets as a deploy step:

npm ci && npm run build

Also make sure public/build isn't in your .gitignore if you deploy with git and don't build on the server. That one has caught me more than once.

4. SQLSTATE[HY000] [1045] Access denied

SQLSTATE[HY000] [1045] Access denied for user 'root'@'localhost' (using password: YES)

Cause: MySQL rejected the credentials Laravel sent. Sometimes they're wrong, and sometimes they're correct in .env but Laravel is still using an older cached copy.

Fix: Check .env first:

DB_HOST=127.0.0.1
DB_DATABASE=my_app
DB_USERNAME=my_user
DB_PASSWORD=

An empty password should be left empty. Don't write null or "". Then clear the cached config:

php artisan config:clear

If the credentials are definitely right, the user may not have access to that database:

GRANT ALL PRIVILEGES ON my_app.* TO 'my_user'@'localhost';
FLUSH PRIVILEGES;

On shared hosting, remember the account prefix (cpaneluser_dbname). If localhost fails, try 127.0.0.1. MySQL treats them differently: one connects over a socket and the other over TCP.

5. Target class does not exist

Illuminate\Contracts\Container\BindingResolutionException:
Target class [HomeController] does not exist.

Cause: The route refers to a controller that Laravel can't resolve. This is usually the old string syntax, a wrong namespace, or a typo in the filename.

Fix: Reference the class directly in your route instead of using a string:

use App\Http\Controllers\HomeController;

Route::get('/', [HomeController::class, 'index']);

Check that the namespace at the top of the controller matches its folder, and that the filename matches the class name exactly, including uppercase and lowercase. Linux is case-sensitive even when your Mac isn't. Then run:

composer dump-autoload
php artisan route:clear

6. Composer: Allowed memory size exhausted

PHP Fatal error: Allowed memory size of 1610612736 bytes exhausted

Cause: PHP's memory_limit for the CLI is too low for Composer to resolve your dependencies. This happens most during composer update.

Fix: Lift the limit for just that one command:

COMPOSER_MEMORY_LIMIT=-1 composer update

On a small VPS, a better habit is to run composer update locally, commit composer.lock, and only run composer install --no-dev on the server. Installing from a lock file uses far less memory than resolving dependencies from scratch.

7. Permission denied on laravel.log

The stream or file "/var/www/app/storage/logs/laravel.log" could not be opened
in append mode: Failed to open stream: Permission denied

Cause: The web server user (www-data, nginx, apache) doesn't own storage/ or bootstrap/cache/. This often happens because you ran an artisan command as root, which created files the web server can't write to.

Fix: Give ownership back to the web server and use sensible permissions:

sudo chown -R www-data:www-data storage bootstrap/cache
sudo chmod -R 775 storage bootstrap/cache

Please don't chmod -R 777. It makes the error go away by letting every user on the box write into your app.

8. CORS blocked the request

Access to fetch at 'http://api.test/api/posts' from origin 'http://localhost:5173'
has been blocked by CORS policy

Cause: The browser is enforcing the Same-Origin Policy. Your frontend and API are on different origins, and the API didn't say that's allowed.

Fix: In Laravel 11, publish the CORS config first, since it isn't there by default:

php artisan config:publish cors

Then set it in config/cors.php:

'paths' => ['api/*', 'sanctum/csrf-cookie'],
'allowed_origins' => ['http://localhost:5173'],
'supports_credentials' => true, // only if you send cookies

Don't also add CORS headers in Nginx or Apache. You'll end up with duplicate headers, which the browser rejects too.

9. Specified key was too long

SQLSTATE[42000]: Syntax error or access violation: 1071
Specified key was too long; max key length is 767 bytes

Cause: You're on an older MySQL or MariaDB version that uses utf8mb4, and an indexed string column is too wide for it.

Fix: In AppServiceProvider::boot():

use Illuminate\Support\Facades\Schema;

Schema::defaultStringLength(191);

Upgrading the database engine is the better long-term fix, but this gets migrations running again.

10. "I changed the config and nothing happened"

This isn't really an error message, but it's behind a lot of the problems above. If you ran config:cache or route:cache on a server, Laravel stops reading .env at runtime and ignores changes to your route files until you rebuild the cache.

php artisan optimize:clear

That one command clears the cached config, routes, views, and events.

My debugging checklist

Before I search for anything, I go through these:

1. Read the full message and the first lines of the stack trace that point to my own files. The answer is usually there.
2. Check storage/logs/laravel.log. Almost every exception ends up in it.
3. Run php artisan optimize:clear. Stale caches pretend to be all kinds of other bugs.
4. Check who owns storage/ whenever an error only happens on the server.
5. Use dd() and dump() to check my assumptions about variables, instead of reasoning about them.
6. Compare .env against .env.example after a deploy or a fresh clone.

This post only covers the errors I hit most often. I keep a longer list of Laravel error fixes here, with a deeper write-up for each one.

Which Laravel error has cost you the most hours? Tell me in the comments. If it's one I haven't covered, I'll probably add it here.