Environment
Platform: Unraid (Docker)
Image: jsonbored/simplelogin-aio:latest
Deployment: Single container, internal Postgres/Redis (no external DB_URI/REDIS_URL)
RELAY_MODE: gmail (SMTP tested successfully with swaks)
Configuration (non‑sensitive excerpt)
URL=https://my.domain.com
EMAIL_DOMAIN=my.domain.com
SUPPORT_EMAIL=support@my.domain.com
RELAY_MODE=gmail
NOT_SEND_EMAIL=false
DISABLE_REGISTRATION=false
OTHER_ALIAS_DOMAINS=[]
ALIAS_DOMAINS=[]
PREMIUM_ALIAS_DOMAINS=[]
...
What I did
Started the container with the above configuration (first boot, fresh /appdata).
Waited for migrations and init to finish (logs show init_app.py completed successfully).
Opened the web UI at https://my.domain.com/auth/register.
Submitted the registration form with a valid email address.
What actually happens
The browser stays on the same page without any visible error.
The HTTP response to POST /auth/register is 200 (no redirect, no error message).
The user is not inserted into the users table (SELECT email, activated FROM users; returns 0 rows).
The simplelogin-job runner shows no log lines indicating it processed a job (no “sending activation email”).
Redis queue simplelogin-job stays at 0 (LLEN simplelogin-job returns 0 right after the POST).
The container logs only show the web request itself:
webapp - DEBUG - "/code/server.py:259" - after_request() - POST /auth/register ImmutableMultiDict([]) 200
Additional tests performed
SMTP connectivity is fine – swaks can send emails through Gmail without issues.
NOT_SEND_EMAIL is explicitly set to false in /code/.env (verified with grep inside the container).
Attached: full container log from startup until two registration attempts.
Request
Could you help me understand why the registration silently fails? Is there any additional logging I can enable to see the exact error returned by the registration endpoint? Happy to provide any further debug information.
Environment
Platform: Unraid (Docker)
Image: jsonbored/simplelogin-aio:latest
Deployment: Single container, internal Postgres/Redis (no external DB_URI/REDIS_URL)
RELAY_MODE: gmail (SMTP tested successfully with swaks)
Configuration (non‑sensitive excerpt)
What I did
Started the container with the above configuration (first boot, fresh /appdata).
Waited for migrations and init to finish (logs show init_app.py completed successfully).
Opened the web UI at https://my.domain.com/auth/register.
Submitted the registration form with a valid email address.
What actually happens
The browser stays on the same page without any visible error.
The HTTP response to POST /auth/register is 200 (no redirect, no error message).
The user is not inserted into the users table (SELECT email, activated FROM users; returns 0 rows).
The simplelogin-job runner shows no log lines indicating it processed a job (no “sending activation email”).
Redis queue simplelogin-job stays at 0 (LLEN simplelogin-job returns 0 right after the POST).
The container logs only show the web request itself:
webapp - DEBUG - "/code/server.py:259" - after_request() - POST /auth/register ImmutableMultiDict([]) 200Additional tests performed
SMTP connectivity is fine – swaks can send emails through Gmail without issues.
NOT_SEND_EMAIL is explicitly set to false in /code/.env (verified with grep inside the container).
Attached: full container log from startup until two registration attempts.
Request
Could you help me understand why the registration silently fails? Is there any additional logging I can enable to see the exact error returned by the registration endpoint? Happy to provide any further debug information.