You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When successfully logging in, I see the full RomM web interface for a fraction of a second, before being redirected to the /login page again. In the logs, 403 errors can be seen for one or more entries.
To Reproduce
Steps to reproduce the behavior:
Run RomM with Podman rootless on RHEL9 (podman 4.9.4) with the command below with an existing MariaDB server on the host OS.
After tracking this down, I have found a workaround, which is to lower the number of gunicorn workers from the default of 2 to only 1: GUNICORN_WORKERS=1
The text was updated successfully, but these errors were encountered:
Good catch! It seems the issue here is that you are providing a ROMM_AUTH_SECRET environment variable, instead of ROMM_AUTH_SECRET_KEY.
When RomM doesn't receive a ROMM_AUTH_SECRET_KEY value, it randomly generates an auth secret. There is a bug here, because when multiple Gunicorn workers are spawn, each of them will generate a different auth secret!
Let's keep the issue open even if changing the environment variable name fixes it for you, so we can fix the underlying randomness.
RomM version
Version 3.5.1
Describe the bug
When successfully logging in, I see the full RomM web interface for a fraction of a second, before being redirected to the /login page again. In the logs, 403 errors can be seen for one or more entries.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No 403 errors and be logged in.
Screenshots
N/A
Desktop
Smartphone
N/A
Additional context
Full Podman command line used:
After tracking this down, I have found a workaround, which is to lower the number of gunicorn workers from the default of 2 to only 1:
GUNICORN_WORKERS=1
The text was updated successfully, but these errors were encountered: