Files
OmniRoute/changelog.d/fixes/9286-redis-loopback-bind.md
Chedrian07 fd62cb1152 fix(docker): publish the Redis sidecar on loopback instead of 0.0.0.0 (#9286)
Validated in local merge-train (devbox-vm-06-dev002) @ combined-tip (FAST gates green: static + changed tests + vitest — only pre-existing audit.test.ts flake). Evidence: /home/diegosouzapw/dev/proxys/OmniRoute/.claude/worktrees/merge-train-20260805-213228-suite.log
2026-08-05 21:45:56 -03:00

655 B

  • fix(docker): the bundled Redis sidecar no longer publishes on 0.0.0.0. docker-compose.yml, omniroute redis up and the dashboard's 1-click launcher all built an unqualified -p <port>:6379 spec, which the container runtime expands to every interface — and none of them sets requirepass, so any host on the LAN could reach the rate-limiter/cache store. All three now default to 127.0.0.1, with exposure opt-in via REDIS_BIND_HOST (compose), --bind (CLI) and OMNIROUTE_REDIS_BIND_HOST (launcher); the CLI warns when a non-loopback bind is requested without --password (#9286)