hermes - 💡(How to fix) Fix Gateway set up

 - User ID 6614365140 (Kelly Hess) is being rejected with:
   WARNING gateway.run: Unauthorized user: 6614365140 (Kelly Hess)
 on telegram
 - Tried the following in ~/.hermes/config.yaml:
   - allowed_chats: '6614365140'
   - allowed_chats: '' + guest_mode: true
 - Neither setting resolved the issue. The gateway continued to
 block the user even after multiple restarts (hermes gateway restart
 and systemctl --user restart).
 - Running the gateway manually (python -m hermes_cli.main gateway
 run) produced the same error.
 Problem 2: Web UI – Persistent password prompt

 - Web UI (bootstrap.py) keeps asking for a password even after:
   - Setting HERMES_WEBUI_PASSWORD=letmein in .env
   - Deleting ~/.hermes/webui/.pbkdf2_key, .signing_key,
 .login_attempts.json, and .sessions.json
   - Running rm -rf ~/.hermes/webui/*
   - Starting with python3 bootstrap.py --host 0.0.0.0
 - Even after a full state wipe, authentication remained enabled.
 - The .env variable does not appear to override the password
 reliably.
 Environment
 - WSL2 on Windows
 - Tailscale active
 - Gateway running as systemd user service
 - Web UI binds correctly to 0.0.0.0:8787 when forced
 Request
 - Clarification on the correct way to whitelist Telegram users
 (allowed_chats / guest_mode)
 - Reliable way to disable or reset Web UI password via environment
 variable or config

 Log & Config Inspection
 bash
 tail -100 ~/.hermes/logs/gateway.log | grep -E
 'telegram|Telegram|httpx|polling'
 cat ~/.hermes/gateway_state.json
 grep -A 5 'telegram:' ~/.hermes/config.yaml
 journalctl --user -u hermes-gateway.service -n 40 --no-pager

 Gateway Management
 bash
 systemctl --user stop hermes-gateway.service
 systemctl --user start hermes-gateway.service
 systemctl --user restart hermes-gateway.service
 systemctl --user status hermes-gateway.service

 Web UI Troubleshooting
 bash
 pkill -f bootstrap.py || true
 rm -f ~/.hermes/webui/.pbkdf2_key ~/.hermes/webui/.signing_key
 ~/.hermes/webui/.login_attempts.json
 rm -rf ~/.hermes/webui/*
 printf 'HERMES_WEBUI_PASSWORD=letmein\nHERMES_WEBUI_HOST=0.0.0.0\n'
 > .env
 python3 bootstrap.py --host 0.0.0.0
 HERMES_WEBUI_PASSWORD=letmein python3 bootstrap.py --host 0.0.0.0

- Main Report: https://paste.rs/M7slg
     - agent.log: https://paste.rs/TxPmH
     - gateway.log: https://paste.rs/pJ7MV

The main recurring error we saw throughout the session is:

     text
     WARNING gateway.run: Unauthorized user: 6614365140 (Kelly Hess) on
     telegram

     This appeared repeatedly in both the gateway logs and journalctl,
     even after:

     - Setting allowed_chats: '6614365140'
     - Adding guest_mode: true
     - Multiple gateway restarts
     - Running the gateway manually

     No full Python traceback was shown — only this authorization
     warning.

 - Added allowed_chats: '6614365140' in ~/.hermes/config.yaml
 - Changed to allowed_chats: '' + added guest_mode: true
 - Restarted the gateway using:
   - hermes gateway restart
   - systemctl --user restart hermes-gateway.service
   - systemctl --user stop/start
 - Ran the gateway manually in foreground (python -m hermes_cli.main
 gateway run)
 - Verified gateway_state.json showed Telegram as connected
 - Checked and cleared old network errors in logs
 Web UI Password Fixes Attempted

 - Set HERMES_WEBUI_PASSWORD=letmein (and other values) in
 /home/kelly/hermes-webui/.env
 - Deleted password/state files:
   - .pbkdf2_key
   - .signing_key
   - .login_attempts.json
   - .sessions.json
 - Ran full state wipe: rm -rf ~/.hermes/webui/*
 - Started Web UI with explicit host: python3 bootstrap.py --host
 0.0.0.0
 - Started with inline env var: HERMES_WEBUI_PASSWORD=letmein
 python3 bootstrap.py
 - Tried accessing from both WSL and Windows host
 (http://localhost:8787)
 Other Actions

 - Ran hermes debug share and uploaded logs
 - Confirmed Python 3.14.4 and Hermes v0.14.0