Web token printed in the startup log #40

New Issue

rays · 2026-09-19T08:16:13-07:00

rays commented

2026-09-19 08:16:13 -07:00

At every start the daemon printed web ui at http://<bind>/?token=<token>. The token signs in as the admin, and in the container that line lands in docker logs, readable by anyone with Docker access on Tower. Found reading production's logs on 2026-09-19.

At every start the daemon printed `web ui at http://<bind>/?token=<token>`. The token signs in as the admin, and in the container that line lands in `docker logs`, readable by anyone with Docker access on Tower. Found reading production's logs on 2026-09-19.

rays added the bug label 2026-09-19 08:16:13 -07:00

rays commented

2026-09-19 08:16:13 -07:00

Fixed in 3625cf4, released in 0.8.3 and deployed: the startup line now says where the token is kept ([web] token in config.toml), never what it is. Checked: docker logs iPodderX | grep -c token= is 0.

Fixed in 3625cf4, released in 0.8.3 and deployed: the startup line now says where the token is kept (`[web] token` in config.toml), never what it is. Checked: `docker logs iPodderX | grep -c token=` is 0.

rays closed this issue

2026-09-19 08:16:14 -07:00

rays referenced this issue from a commit

2026-09-19 08:16:36 -07:00

CLAUDE.md: the tea example uses the token issue's real number, #40

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: rays/ipodderx-rs#40