Skip to content
Grav 2.0 is officially stable. Read the announcement →

Community guidelines

Please keep discussions civil and on-topic. Repeated violations may lead to a temporary ban.

Support

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

admin

Started by saeed 10 months ago · 3 replies · 120 views
10 months 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

10 months ago

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

Suggested topics

Topic Participants Replies Views Activity
Support · by Thomas, 1 week ago
2 50 6 hours ago
Support · by Anna, 2 days ago
2 58 9 hours ago
Support · by Justin Young, 10 hours ago
1 28 10 hours ago
Support · by Duc , 1 week ago
2 63 5 days ago
Support · by Colin Hume, 1 week ago
2 53 5 days ago