From 1eaa1c42ebd47945624b8231334ce8f27fe3f297 Mon Sep 17 00:00:00 2001 From: Casey Dwyer Date: Mon, 25 Aug 2025 11:57:27 -0500 Subject: [PATCH 1/2] Update control-panel-page-expired.md --- .../troubleshooting/control-panel-page-expired.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/collections/troubleshooting/control-panel-page-expired.md b/content/collections/troubleshooting/control-panel-page-expired.md index 1725d466e..e1a852282 100644 --- a/content/collections/troubleshooting/control-panel-page-expired.md +++ b/content/collections/troubleshooting/control-panel-page-expired.md @@ -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 a successful login. You can workaround this by changing the `user_id` column to a string/varchar: From 81dd2f1e04ddc7c04393d985bb5daab4de5241ea Mon Sep 17 00:00:00 2001 From: Casey Dwyer Date: Mon, 25 Aug 2025 12:07:42 -0500 Subject: [PATCH 2/2] language tweak --- .../collections/troubleshooting/control-panel-page-expired.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/collections/troubleshooting/control-panel-page-expired.md b/content/collections/troubleshooting/control-panel-page-expired.md index e1a852282..6c356f24f 100644 --- a/content/collections/troubleshooting/control-panel-page-expired.md +++ b/content/collections/troubleshooting/control-panel-page-expired.md @@ -11,7 +11,7 @@ There are a few common reasons why you might encounter a "419 Page Expired" erro ## 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 either a 419 error or a continuous redirect back to the login form—even after a successful login. +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: