Can't login after install (docker)

[itlists]

Hello,
I've deployed this on unRaid as a docker container. When trying to login with admin/admin, the webUI comes back with error "Your session has expired. Please log in again."
I've done multiple fresh installs, same problem.

Any suggestions please? Thanks

[matteius]

Are you using the published container on the GH repository or are you building it yourself?

[itlists]

Success after update! Thank you

[itlists]

Noticed some strange behaviours when going through the webUI. eg users list was empty even after adding a user.
Deleted the container, re-installed and now the same login issue occurs again - session expired error.

[matteius]

Ill investigate this but know that the user account management hasn't had a lot of TLC yet -- can you tell me more about your use case so I can try to factor that in?

[itlists]

Pretty basic use case. I have 4 cameras around my residence. I want them to record video + audio whenever there's motion in specified zones. The recordings should be stored for at least 30 days (there is enough disk space), and be accessible via the webUI for review.
The app should allow for multiple users and roles (eg: viewer, admin, etc.).

[matteius]

The release from today had user management improvements in it -- also started working on a test CI that covers basic cases.

[itlists]

Thank you for the quick updates.
After upgrading to new release, the container goes into boot loop - shuts down during the startup process and tries to restart.
I'll perform a clean install later and try.

[matteius]

Based on my testing, I cannot reproduce the boot loop issue. The Docker container works correctly in all scenarios I tested:

Fresh start without volumes - Works fine
Fresh start with mounted volumes - Works fine
Upgrade scenario with old-style config (missing go2rtc section) - Works fine
The container:

Status: Up (healthy)
RestartCount: 0
Initializes successfully and starts the web server on port 8080

Possible causes for the user's boot loop:

Port conflicts - Another service using ports 8080, 1984, 8554, or 8555
Volume permission issues - Especially on NFS mounts (the user in issue #67 uses NFS)
Corrupted database - An existing database from a much older version that fails migration
Docker restart policy - If using restart: always with a crash, it will loop
Resource constraints - Memory limits causing OOM kills
Recommendations for the user:

Check container logs: docker logs <container_name>
Check for port conflicts: netstat -tlnp | grep -E '8080|1984|8554|8555'
Try a clean install by removing existing config/data volumes
Check if there's an existing go2rtc process running outside the container
Check Docker events: docker events --filter container=<container_name>