Repository navigation
Login #6
Description
What broke
Login to services. After installation the username and password from admin.txt doesn't allow login to services
OS and version
LXC unprivilidged (Debian 13) on Proxmox v9.2.21 x64
arrstack version
1.2.0
arrstack doctor output
System checks
✓ Not running as root: Running as a normal user
✓ Docker installed: Docker is installed
✓ Docker running: Docker daemon is running
✓ Docker Compose v2: Docker Compose v2 is available
✓ Disk space on /: 20GB available (need 10GB)
✓ Disk space on /mnt/data: 160GB available (need 10GB)
Container status
✓ qBittorrent: running (health: healthy)
✓ Prowlarr: running (health: healthy)
✓ Sonarr: running (health: healthy)
✓ Radarr: running (health: healthy)
✓ Bazarr+: running (health: healthy)
✓ Jellyfin: running (health: healthy)
✓ Jellyseerr: running (health: healthy)
✓ Recyclarr: running
✓ Trailarr: running (health: healthy)
✓ Gluetun: running (health: healthy)
✓ Caddy: running
✓ Deunhealth: running (health: healthy)
✓ FlareSolverr: running (health: healthy)
✓ AI Subtitle Translator: running (health: healthy)
HTTP health checks
✓ AI Subtitle Translator: http://localhost:8765/health → 200
✓ FlareSolverr: http://localhost:8191/health → 200
✓ Sonarr: http://localhost:8989/ping → 200
✓ Prowlarr: http://localhost:9696/ping → 200
✓ qBittorrent: http://localhost:8080/ → 200
✓ Radarr: http://localhost:7878/ping → 200
✓ Trailarr: http://localhost:7889/status → 200
✓ Jellyseerr: http://localhost:5055/api/v1/status → 200
✓ Bazarr+: http://localhost:6767/api/system/ping → 200
✓ Jellyfin: http://localhost:8096/health → 200
Reproduce
Fresh Install. Fails on recyclarr because of other issue. Followed the solution provided as workaround.
Logs
All services has stared successfully
Anything else
No
Activity
LavX commentedon Oct 19, 2026
Thanks for the report. This is a side effect of the Recyclarr pull failure, not a bad password.
The installer writes
admin.txtbefore it touches Docker, but the Sonarr/Radarr/Prowlarr admin users and the Jellyfin admin user are created in the wiring steps that run after the containers are healthy. The install aborted atdocker compose pull, so it never reached them. Starting the containers manually withdocker compose up -dgives you healthy containers with no login user.Fixed in v1.2.1 (https://github.com/LavX/arrstack/releases/tag/v1.2.1):
ghcr.io/recyclarr/recyclarr:8, so fresh installs get past the pull step.arrstack updatenow seeds a missing Sonarr/Radarr/Prowlarr admin user fromadmin.txt.arrstack doctorreports an incomplete install whenstate.jsonhas noinstall_completed_at.To recover your existing install:
curl -fsSL https://lavx.github.io/arrstack/install.sh | bash arrstack install --resume--resumereuses your state and admin password, then runs the full wiring pipeline, including the Jellyfin setup thatarrstack updatedoes not cover. If only the arr logins are broken and Jellyfin is already configured,arrstack updateis enough.I verified the seed path against fresh LinuxServer Sonarr 4.0.19, Radarr, and Prowlarr containers: seeding returns success,
POST /loginreturns a valid auth cookie, and re-running it does not overwrite an existing user.LavX commentedon Oct 19, 2026
End-to-end verification with the released v1.2.1 binary, not just unit tests:
I simulated the exact failure: a fresh
state.jsonwith noinstall_completed_at, Sonarr/Radarr/Prowlarr started but unseeded, andadmin.txtpresent. Before the update, all threeGET /api/vN/config/hostcalls returned empty usernames andPOST /loginredirected tologinFailed=true.Then I ran the downloaded v1.2.1 release binary:
After that,
POST /loginreturned 302 to/with an auth cookie on all three services, andGET /config/hostshowedusername: admin,authenticationMethod: forms,authenticationRequired: enabled.arrstack doctoralso correctly flagged the incomplete install and pointed atarrstack install --resume. For Jellyfin, still use--resume, sinceupdateonly repairs the arr logins.