Binions listens on exactly one network address — and you set it in exactly one place. That single setting flows automatically into the part of Binions that faces your network (the edge), into the systemd service environment, and into the TLS certificate. There are no IP addresses scattered across config files to hunt down and keep in sync.
What "bind address" means. It is the IP address the Binions edge listens on for clients on your network — the address you (or other machines on your LAN) point a browser or script at to reach Binions over HTTPS.
The bind address has a single source of truth: a platform setting Binions reads when it starts. You never edit it by hand in several files. Once it is set, Binions propagates it for you to every place that needs it:
The key idea. Set the address once; the edge binding, the service environment, and the certificate all derive from it. There are no hardcoded IP addresses to chase across files, and nothing can drift out of sync.
The bind address applies to one thing only: the edge. The edge is the reverse proxy that accepts requests from your network and forwards them inward. It listens on your LAN address on a main HTTPS edge (:8443) and an HTTP redirect (:8081, which only sends plain HTTP straight to HTTPS), plus a few dedicated, authenticated entry points for the platform’s bundled admin tools — the Traefik dashboard on :8444, the MinIO console on :8445, and the Showman hub on :8446. These are all entry points of the one edge process; the full list lives in Network requirements.
Everything else stays on 127.0.0.1 (loopback) — reachable only from the host itself, never from the network. The internal services Binions runs to coordinate work are deliberately not exposed:
| Component | Listens on | Reachable from the network? |
|---|---|---|
Edge — HTTPS (:8443) | Your LAN bind address | Yes — this is the front door |
Edge — HTTP redirect (:8081) | Your LAN bind address | Yes — redirects to HTTPS only |
Edge — Traefik dashboard (:8444) | Your LAN bind address | Yes — authenticated admin tool |
Edge — MinIO console (:8445) | Your LAN bind address | Yes — authenticated admin tool |
Edge — Showman hub (:8446) | Your LAN bind address | Yes — authenticated admin tool |
Per-daemon health endpoints (:91xx) | 127.0.0.1 | No |
| Redis (internal event bus) | 127.0.0.1 | No |
| PostgreSQL (storage) | 127.0.0.1 | No |
| MinIO (object storage) | 127.0.0.1 | No |
| Jaeger (tracing) | 127.0.0.1 | No |
Closed by default. Only the edge is ever bound to your network address. The internal services — databases, object storage, the event bus, health checks, and tracing — stay on loopback and cannot be reached from the LAN. This is a deliberate defense-in-depth choice: the only network-facing process is the one edge router, presenting a small set of authenticated entry points and nothing more.
You set the bind address with the bootstrap tool. The simplest option is auto, which detects the host's primary IP address for you (the address the host would use to reach the outside world):
sudo binions-bootstrap --bind-address autoIf you would rather name the address explicitly — for example, the host has more than one interface and you want to be precise about which one Binions uses — pass it directly:
sudo binions-bootstrap --bind-address 10.0.0.5Either way, bootstrap does the rest: it records the address as the single source of truth, writes the service environment, fills in the edge configuration, regenerates the certificate if needed, and restarts the edge so the change takes effect. The edge’s port numbers are fixed platform defaults — bootstrap only sets the address they listen on, never the ports themselves.
Safe to re-run. Bootstrap is idempotent — running it again with the same address changes nothing, and the certificate is only regenerated when it actually needs to be. You can run it freely after any change without worrying about side effects.
Because the address lives in one place and flows outward automatically, moving Binions to a new host — or simply changing which address it serves — is just re-running bootstrap on the new machine:
sudo binions-bootstrap --bind-address autoFrom that one command, Binions updates everything that depends on the address:
For setting Binions up across more than one machine, see the Multi-host install guide. For how the certificate and the edge fit together, see TLS & the Traefik edge.