Upgrade & Secure Your Future with DevOps, SRE, DevSecOps, MLOps!

We spend hours scrolling social media and waste money on things we forget, but won’t spend 30 minutes a day earning certifications that can change our lives.
Master in DevOps, SRE, DevSecOps & MLOps by DevOps School!

Learn from Guru Rajesh Kumar and double your salary in just one year.


Get Started Now!

Fixing Laravel Migration Error: “Unknown Collation: utf8mb4_0900_ai_ci”

While working with Laravel and MySQL, you might run into an error during migrations like this one:

Illuminate\Database\QueryException
SQLSTATE[HY000]: General error: 1273 Unknown collation: 'utf8mb4_0900_ai_ci'

Why This Happens

The collation utf8mb4_0900_ai_ci is introduced in MySQL 8.0. If you’re using an older version of MySQL (like 5.7 or earlier), it doesn’t recognize this collation, and Laravel throws this error during migrations or queries.

Laravel 10+ and Laravel 11 use this collation by default in their database config, assuming the database supports it.


How to Fix It

There are two common ways to fix this issue:

🛠 Option 1: Downgrade the Collation in config/database.php

Open the config/database.php file in your Laravel project.

Locate the mysql connection settings and change the collation and charset like this:

'mysql' => [
    'driver' => 'mysql',
    'host' => env('DB_HOST', '127.0.0.1'),
    'port' => env('DB_PORT', '3306'),
    'database' => env('DB_DATABASE', 'your_db_name'),
    'username' => env('DB_USERNAME', 'root'),
    'password' => env('DB_PASSWORD', ''),
    'charset' => 'utf8mb4',
    'collation' => 'utf8mb4_unicode_ci', // Change this line
    ...
],

Then, clear the config cache:

php artisan config:clear

Now try running the migration again:

php artisan migrate

Option 2: Upgrade Your MySQL Server

If possible, upgrade your MySQL server to version 8.0 or higher, which fully supports utf8mb4_0900_ai_ci.

This is ideal for production servers or when you need access to newer MySQL features.

This is a common issue when developing Laravel apps locally on XAMPP, WAMP, or older MySQL versions. Fortunately, a simple config change is usually all you need to get back on track.

Pro Tip: Always make sure your development and production environments use compatible database versions and configurations to avoid such surprises.

Related Posts

Fixing the “Could not find PHP executable” Error in Live Server on VS Code

this is a common issue and easy to fix! This guide will walk you through the step-by-step solution to get your PHP files running in the browser….

How to Fix the “npm.ps1 cannot be loaded” Error on Windows When Running npm start

If you’re a developer working with React or any Node.js-based projects, you may have encountered the following error when trying to run npm start in PowerShell on…

Simplify Database Migrations with kitloong/laravel-migrations-generator in Laravel

Laravel provides a powerful migration system that allows developers to easily define and manage database schema changes. However, when working with legacy databases or large projects, manually…

Understanding and Fixing the “Unable to Read Key from File” Error in Laravel Passport

Laravel Passport is a powerful package for handling OAuth2 authentication in Laravel applications. It allows you to authenticate API requests with secure access tokens. However, like any…

How to Generate a GitHub OAuth Token with Read/Write Permissions for Private Repositories

When working with GitHub, you may need to interact with private repositories. For that, GitHub uses OAuth tokens to authenticate and authorize your access to these repositories….

Laravel Error: Target class [DatabaseSeeder] does not exist – Solved for Laravel 10+

If you’re working with Laravel 10+ and run into the frustrating error: …you’re not alone. This is a common issue developers face, especially when upgrading from older…

0 0 votes
Article Rating
Subscribe
Notify of
guest
0 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x