mirror of
https://github.com/pocket-id/pocket-id.git
synced 2026-02-27 08:00:56 +03:00
🐛 Bug Report: Cannot create admin user - redirect to /login from /setup #423
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @importantblimp on GitHub (Aug 17, 2025).
Reproduction steps
My setup is a little unusual, so it's entirely possible I'm doing something wrong, but I'd appreciate any guidance you might have:
I'm running Pocket-id frontend and backend on a server through the systemd services defined in NixOS.
I've forwarded the frontend port (3005) through SSH to my localhost where I connect to it in the browser.
I'll replace this with a reverse proxy after setting up the admin user.
Unfortunately I can't reach
/setupto create the first admin user - I get redirected to/login.As a result I can't use a passkey or one time login token because I haven't been able to setup any users yet.
Expected behavior
Not redirect from
/setup, and allow the user to create an admin user.Actual Behavior
The images also result in HTTP 303 responses.
From local machine:
Version and Environment
Version: 0.53.0
Environment variables:
Although TRUST_PROXY is set, it's not currently behind a reverse proxy.
Log Output
Backend service logs when hitting
/login:Navigate to
/setup:The same thing happens using
curlon the server itself:$ curl -Lv localhost:3005/setupThere's only one row in the database, in the
schema_migrationstable. The other tables are empty:@ItalyPaleAle commented on GitHub (Aug 17, 2025):
Version: 0.53.0
Please update to v1.7.0 as that version is not supported anymore
@importantblimp commented on GitHub (Aug 17, 2025):
I've been attempting to for the last hour or so (NixOS stable doesn't make this easy).
I did just get it working though - and it's fixed both the redirect and image issue.
I did notice that the environment variables changed between versions, and I wasn't using the right ones for 0.53.0.
That doesn't explain why the database connection worked though.
Anyway, it works now.
Thanks for the response and sorry for the spurious bug report.