Skip to content
Grav 2.1 is out: every page speaks Markdown. Read the announcement →

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 · 482 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 complanar, 6 days ago
6 140 17 hours ago
Support · by Rick Beebe, 6 days ago
2 100 2 days ago
Support · by blu3prince, 3 days ago
0 52 3 days ago
Support · by alex, 4 days ago
2 92 3 days ago
Support · by Marcel, 2 weeks ago
1 143 4 days ago