14:21:31 3.4 a stranger's sign-up POST /api/auth/register -> 403 '{"detail":"Registration is currently disabled"}'
14:21:31 3.4 the sign-up PAGE GET /register -> 200 (the SPA; the call behind it is refused above)
14:21:32 3.9 browser sign-in through traefik with an https Origin: right password -> 200 token=yes; wrong -> 400 '{"detail":"LOGIN_BAD_CREDENTIALS"}'
14:21:32 3.9 the token reads the account: GET /api/users/me -> 200, e-mail matches=True
14:21:32 3.9 the same without a token -> 401
14:22:36 3.10 one failed sign-in per shape, then the rate-limit keys the backend wrote (key = the address it believed):
14:22:46    tunnel visitor A: XFF '198.51.100.66' -> 400; keys now ['rate_limit:/api/auth/login:198.51.100.66']
14:22:52    tunnel visitor A, forged leftmost: XFF '10.0.0.5, 198.51.100.66' -> 400; keys now ['rate_limit:/api/auth/login:198.51.100.66']
14:23:00    tunnel visitor B: XFF '198.51.100.77' -> 400; keys now ['rate_limit:/api/auth/login:198.51.100.66', 'rate_limit:/api/auth/login:198.51.100.77']
14:23:03    LAN visitor (DooPlex, no XFF) -> 400; keys now ['rate_limit:/api/auth/login:198.51.100.66', 'rate_limit:/api/auth/login:198.51.100.77', 'rate_limit:/api/auth/login:unknown']
14:23:06 3.6 lock-out: 8 wrong passwords from tunnel visitor A, then the household's right password from A, from B, from the LAN:
14:23:37    A's 8 wrong tries: ['400', '400', '400', '400', '400', '429', '429', '429']
14:23:41    A, right password -> 429
14:23:44    B, right password -> 400
14:23:44    LAN, right password -> 200
14:23:48    A forging a new leftmost entry, right password -> 429
14:24:53    A, right password 61 s later -> 400
14:24:54 3.7 the admin creates a family member: POST /api/admin/users -> 201 '{"id":"<id>","email":"csalad5df7f4@drill.felhom.eu","is_active":true,"is_superuser":false,"is_verified":true,"preference'
14:24:54 3.7 the family member signs in -> 200 token=yes
14:24:54 3.7 the member changes the own password: PATCH /api/users/me -> 200; old password now -> 400, new -> 200
14:24:54 3.7 the family member (not admin) cannot create users: POST /api/admin/users -> 403
14:24:54 2.8 could not read the seeded transaction's id: 401 '{"detail":"Unauthorized"}'
14:24:54 1.8 an unknown API path -> 404 '{"detail":"Not Found"}' (a stack trace would show 'Traceback' or 'File "')
14:24:58 1.5 the server processes: securo-backend: /usr/local/bin/python3.14 /usr/local/bin/uvicorn app.main:app --host 0.0.0.0 --port 8000 
securo-worker: /usr/local/bin/python3.14 /usr/local/bin/celery -A app.worker worker --loglevel=info --concurrency=1 
securo-beat: /usr/local/bin/python3.14 /usr/local/bin/celery -A app.worker beat --loglevel=info --schedule /tmp/celerybeat-schedule 

14:25:01 2.7 sizes: 13 MB
4.0K	/app/data/attachments

14:25:16 4.4 securo-backend STOPPED: the controller's state over time [(5, 'running'), (10, 'degraded')]; front door /api/health -> 502
14:25:35     securo: the seeded user cannot sign in (429)
14:25:35 4.4 started again: state running after ~15 s; seed reads back: False
