If you’re trying to sync MySQL changes across Laravel environments, the usual approach is to rely on Laravel migrations rather than trying to manually sync the database. Make sure both environments are pointing to the correct database in the .env file, then run php artisan migrate to apply any pending schema changes. If things got out of sync badly, you can use php artisan migrate:status to see what’s missing, or in development use php artisan migrate:fresh to rebuild the schema from migrations. For data movement between environments, using mysqldump or Laravel seeders is usually safer than trying to copy tables manually.

Also check that both environments are running compatible MySQL versions and the same charset/collation settings, because mismatches there can cause sync issues.

If the sync problem is happening because some tables became corrupted or MySQL cannot read them properly, then native tools may fail to export them. In that situation, try some third party recovery tools like Stellar Repair for MySQL can sometimes help extract data from damaged tables before reimporting them into a clean database.

This issue happens because MySQL limits indexed string lengths, especially when using utf8mb4 (each character = 4 bytes). Your email column with a unique index exceeds that limit.

You can fix it permanently by opening App\Providers\AppServiceProvider.php and adding this inside the boot() method:

use Illuminate\Support\Facades\Schema;

public function boot(): void { Schema::defaultStringLength(191); }

Then run your migration again it’ll work fine.

Alternatively, if you’re on an older MySQL version, consider upgrading to MySQL 5.7+ and enabling innodb_large_prefix for better compatibility.

That SQLSTATE[HY000] [2002] Connection refused error usually means Laravel can’t reach your MySQL server not that the sessions table itself is broken. It’s common after updates or on shared hosts.

Try this:

In your .env, set DB_HOST=127.0.0.1 (not localhost) and recheck the username/password.

Run:

php artisan config:clear php artisan cache:clear

Some hosts use a different socket, like /tmp/mysql.sock, so you might need:

DB_SOCKET=/tmp/mysql.sock

Make sure your .env file is actually being loaded — some shared hosts ignore it.

If the issue persists, your MySQL instance might’ve gotten corrupted or disconnected. Running a quick repair using a tool like Stellar Repair for MySQL can help restore stability before reconnecting Laravel.