419 page expired after upgrading to backpack 6 (and Laravel 10)

[de-raaf-media]

Hi,

I just finished all the upgrade steps to upgrade to BP 6 (from 5). I now get a message 419 page expired when I edit a crud. I know this has to do with CSRF tokens but I cannot explain why this is the case.

Did I miss a step?
Mark

[pxpm]

Hey @de-raaf-media

I've experienced this myself and was due to permissions in the storage folder.

I experienced this with Homestead, is that what you are using ?

I tried it on windows, and had to make some changes in the vagrant file to assign the www-user as the owner of the project, has "vagrant" was taking over it.

Also I was trying to use a custom folder: c:\work, that don't have full read/write permissions (on windows) and had to change the project to c:\Users\MYUSERXXX\work.

If not you can also try a php artisan cache:clear and php artisan basset:clear (also make sure you are using BASSET_DEV_MODE=true in development to exclude any asset bugs)

Let me know how it goes.

[de-raaf-media]

Hi Pedro, I cleared the cache in the last step of the upgrade.

php artisan config:clear
php artisan cache:clear
php artisan view:clear

I now also cleared basset. There is now a basset folder in my storage so that seems to work fine. I am using Laravel Valet by the way.

It seems to be related to XHR routes like admin/page/search.

Mark

[pxpm]

It happened to me on the pre-flight, but like I said, I think the reason was that the sessions were not properly persisted due to folder permissions.

Can you check your browser console and network tab for errors?

Also do your APP_URL in .env is set correctly as the url your use in your browser ?

Cheers

[de-raaf-media]

I just updated my home office version as well. There it seems to work fine. So I'll have to check the office .env version. To be continued ;-)

[tabacitu]

Maybe it's a session issue? Do you have the same problem in an incognito window @de-raaf-media ? If so, a force logout would probably fix it (manually access the /admin/logout url).

[de-raaf-media]

That did not fix it but on another PC it is working fine. Maybe an env file issue

[tabacitu]

Are you sure your APP_URL is set correctly in your .ENV file?

[de-raaf-media]

Hi @tabacitu, @pxpm, this was indeed an .env file issue. I had no https in the URL for some reason. In my test application I do have https. In BP5 this was not an issue but in BP6 it is apparently. Thanks for the help guys.

[Fab-TOK]

Thanks you too much. It worked for me too.
I had the same problem and it blocked me for days.
All you have to do is change the "APP_URL" variable in the .env file of the Laravel project.
Mine used to be "APP_URL=localhost", but that didn't work.
Then I changed it to "APP_URL=http: //movie.test" and it worked.
knowing that "http: //movie.test" is the local domain name I created for my project.
So all you have to do is change the "APP_URL" variable to the correct address. :-)

[tabacitu]

Thanks for the feedback everyone! Good news: we are adding a "check" after the installation, so new people don't run into this problem. Actually they might still run into this problem, but they'll get suggestions on how to fix it right away if their env/config is misconfigured for some reason - Laravel-Backpack/basset#72

[Fab-TOK]

Tell me what is the value of APP_URL now in the file .env ? Le jeu. 20 juil. 2023 à 21:31, Joaquín Borges ***@***.***> a écrit :

…

I use 127.0.0.1:8000/admin to access, what should I put in my APP_URL? — Reply to this email directly, view it on GitHub <#576 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVO4E5VZ2X2TGNM23FL63SDXRGIQJANCNFSM6AAAAAA2MXWXPE> . You are receiving this because you commented.Message ID: <Laravel-Backpack/community-forum/repo-discussions/576/comments/6503319@ github.com>

[JoacinB]

APP_URL=127.0.0.1

[Fab-TOK]

try to change it to APP_URL=127.0.0.1/8000 save the file and refresh the web page Le ven. 21 juil. 2023 à 02:08, Joaquín Borges ***@***.***> a écrit :

…

APP_URL=127.0.0.1 — Reply to this email directly, view it on GitHub <#576 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVO4E5REIA5JRKXLLACM5VTXRHJARANCNFSM6AAAAAA2MXWXPE> . You are receiving this because you commented.Message ID: <Laravel-Backpack/community-forum/repo-discussions/576/comments/6504717@ github.com>

[Fab-TOK]

ooh my bad, instead APP_URL=127.0.0.1:8000 not /8000 Le ven. 21 juil. 2023 à 08:10, fabrice tokoudagba ***@***.***> a écrit :

…

try to change it to APP_URL=127.0.0.1/8000 save the file and refresh the web page Le ven. 21 juil. 2023 à 02:08, Joaquín Borges ***@***.***> a écrit : > APP_URL=127.0.0.1 > > — > Reply to this email directly, view it on GitHub > <#576 (reply in thread)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AVO4E5REIA5JRKXLLACM5VTXRHJARANCNFSM6AAAAAA2MXWXPE> > . > You are receiving this because you commented.Message ID: > <Laravel-Backpack/community-forum/repo-discussions/576/comments/6504717@ > github.com> >

[JoacinB]

Tried both but no success

[JoacinB]

This url works and shows the user 1 data: http://127.0.0.1:8000/admin/user/1/show
But this one returns error 419: http://127.0.0.1:8000/admin/user

[JoacinB]

I found the solution guys!!!

There is a file named datatables_logic.blade.php which has configurations for an AJAX request at line 266:

I added:

              "headers": {
                'X-CSRF-TOKEN': '<?php echo e(csrf_token()); ?>'
              },

and it worked!!!

[mollevi]

worked.

[sadorect]

I have implemented all the suggestions here and there has been no change still.
I'm using
Laravel 10.15
Backpack 6
APP_URL is correct
csrf_token is included on page when you check the page source.

On the list page, the 419 error only shows on a frame which disappears after you click outside but, then, the Data is not listed which is the actual concern.

I have cleared cache all the time. What more is there to do please?

[pxpm]

@sadorect please check in developer console if common.js is beeing loaded correctly.

[sadorect]

Thank you @pxpm
Amazingly, I just found it resolved after I hibernated the PC and came back to it. Not that the hibernation was deliberately targetted at the problem, I only needed to get away from the system and when I came back, we're in business.

Thanks a lot!

[colincameron]

I'm getting the same error on a clean installation of Backpack 6 on Laravel 10. My issue was with the new Basset library and a local Docker environment. I had to add the php artisan storage:link command to my Dockerfile for the asset directory to be created.