Skip to content
● Meet Grav Guard: keep every Grav site you run secure and up to date, all from one place. Free for up to 3 sites. Read more →

Invalid Security Token” after updating to Grav v1.8.0-beta.4 (Admin v1.10.49)

admin

Started by saeed 1 year ago · 3 replies · 719 views
1 year ago

Hello,

I recently updated to Grav v1.8.0-beta.4 with Admin v1.10.49.
Since the update I keep getting “Invalid Security Token” on the Admin login (see screenshot).

What I tried:

Cleared Grav cache (bin/grav clearcache) and browser cache

File/folder permissions are OK (writable: user/, cache/, logs/, tmp/, images/, assets/, backup/)

Interesting behavior:

I can log in via Chrome Incognito.

After logging out and trying to log in again (normal window), I immediately get “Invalid Security Token” again.

Any ideas what changed in 1.8 beta that could cause this? Is there a session/cookie setting I should

image|690x486

1 year ago

Try clearing cookies and sessions

👍 1
1 year ago

I did but, didn’t resolve the issue!
Any other solution?!

Suggested topics

Topic Participants Replies Views Activity
Support · by TomW, 1 day ago
2 33 2 hours ago
Support · by Anna, 1 week ago
2 143 1 day ago
Support · by Anna, 3 weeks ago
1 299 3 weeks ago
Support · by webmasterodp, 1 month ago
4 400 1 month ago
Support · by nwhitfield, 1 month ago
2 373 1 month ago