Laravel 419 proxy reauthentication required

I have an application and i'm hosting it on a subdomain in shared hosting. I was able to send post requests yesterday noon. I woke up today, and all my post requests are getting 419 including sanctum. I have this line in main layout app.blade.php;

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

I have csrf at my forms;

<form action="{{ route('roles.store') }}" method="POST">
                    @csrf

Still i'm getting 419 even with sanctum's default login/register pages. Any ideas?

Kind regards.

LaryAI

3 years ago

Level 58

The 419 error usually occurs when the CSRF token is not being sent or is invalid. Here are a few things you can try:

Clear your browser cache and cookies and try again.
Make sure that the APP_URL in your .env file is set correctly to the subdomain where your application is hosted.
Check if the SESSION_DOMAIN in your .env file is set correctly. If you are using a subdomain, it should be set to .example.com (replace example.com with your domain name).
Try adding the following line to your VerifyCsrfToken middleware:
```
protected $addHttpCookie = true;
```
This will add a XSRF-TOKEN cookie to the response, which can be used by JavaScript frameworks to send the CSRF token in AJAX requests.
If you are using a load balancer or a reverse proxy, make sure that it is configured to forward the X-CSRF-TOKEN header.
If none of the above solutions work, try disabling CSRF protection temporarily to see if the problem is related to CSRF. You can do this by commenting out the VerifyCsrfToken middleware in your App\Http\Kernel file:
```
protected $middlewareGroups = [
    'web' => [
        // \App\Http\Middleware\VerifyCsrfToken::class,
        // ...
    ],
    // ...
];
```
Note that disabling CSRF protection is not recommended in production environments.

If none of the above solutions work, please provide more information about your hosting environment and any relevant error messages.