Laravel CSRF Token Exception in AWS Production Environment with Nginx Load Balancer

Question

I have deployed a Laravel 11 application on AWS using Application Load Balancer (ALB) with Nginx as the web server. I’m using Redis for session and cache management. The application is built with Laravel Jetstream for user authentication. However, users are frequently encountering the following error when performing authenticated actions:

Illuminate\Session\TokenMismatchException: CSRF token mismatch.

What I Have Tried

1. Set up sticky sessions on the ALB using IP-based session affinity to maintain session consistency.
2. Added proxy_set_header X-CSRF-TOKEN $http_x_csrf_token to Nginx configuration.
3. Cleared and cached configuration using php artisan config:clear and php artisan config:cache.
4. Verified that the Redis session store is working and consistent across instances.

Problem Despite these measures, the CSRF token mismatch error persists intermittently for some users. This occurs particularly when accessing forms or submitting data. It seems related to session handling or request routing by the load balancer.

Questions

1. How can I ensure CSRF tokens are properly synchronized across instances when using Redis sessions and an AWS load balancer?
2. Are there additional Nginx or Laravel configurations required to resolve this issue in a multi-instance setup?
3. Should I configure Laravel differently to manage sessions more
   effectively in this architecture?

Any insights or suggestions are appreciated. Let me know if more details are needed!

Here is the SS of error:

Here is VerifyCSRFToken Code: