Skip to content

Broaden context for "control-panel-page-expired" #1727

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: 5.x
Choose a base branch
from
Open

Broaden context for "control-panel-page-expired" #1727

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1eaa1c4
Update control-panel-page-expired.md
caseydwyer Aug 25, 2025
81dd2f1
language tweak
caseydwyer Aug 25, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions content/collections/troubleshooting/control-panel-page-expired.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,17 +1,17 @@
---
id: 3faef3ae-8673-42ba-901b-a1d7eb3db4b7
blueprint: troubleshooting
title: '"419 Page Expired" error when logging into the Control Panel'
title: '"419 Page Expired" error or infinite auth loop when logging into the Control Panel'
categories:
- troubleshooting
template: page
---
There are a few common reasons why you might encounter a "419 Page Expired" error when attempting to login to the Control Panel.
There are a few common reasons why you might encounter a "419 Page Expired" error or an infinite authentication loop/redirect when attempting to login to the Control Panel.

## Database session driver
The most common reason you'll see this error is if you're using the [`database` session driver](https://laravel.com/docs/session#database).

The `user_id` column on the `sessions` table expects an integer value. However, because Statamic uses UUIDs for user IDs, the session row is saved incorrectly, causing the 419 error.
The `user_id` column on the `sessions` table expects an integer value. However, because Statamic uses UUIDs for user IDs, the session row is saved incorrectly, causing either a 419 error or a continuous redirect back to the login form—even after correct login credentials are provided.

You can workaround this by changing the `user_id` column to a string/varchar:

Expand Down