Lock down Postgres/EMQX/API ports, make Tailscale actually exclusive

[david-hummingbot]

Summary

• Postgres (5432) and every EMQX port (1883/8883/8083/8084/8081/18083/61613) now bind to 127.0.0.1 only in docker-compose.yml. Nothing external ever needs these — hummingbot-api reaches them over the emqx-bridge docker network, and bot containers (network_mode=host) reach 127.0.0.1 just as well as 0.0.0.0. This closes a real gap: Docker publishes ports on all interfaces via its own iptables rules, ahead of a plain ufw/host firewall, so these were reachable externally on any VPS deploy regardless of firewall config.
• hummingbot-api's port 8000 is now bound via ${API_BIND_HOST:-0.0.0.0} (default unchanged, so non-Tailscale deploys aren't affected). setup.sh sets API_BIND_HOST=127.0.0.1 whenever Tailscale is enabled.
• The Tailscale sidecar actually proxies port 8000 now. Previously, enabling Tailscale joined the tailnet but port 8000 stayed published on every host interface at the same time — the README's "not exposed publicly" claim wasn't actually enforced. docker-compose.tailscale.yml now sets TS_SERVE_CONFIG (a static, committed tailscale-serve.json) so the sidecar forwards the tailnet IP's :8000 to 127.0.0.1:8000 (reachable directly since the sidecar shares the host's network namespace via network_mode: host).
• make tailscale-status now also prints tailscale serve status so the proxy — not just tailnet membership — is visible.
• README updated to match (port table, Tailscale section, Configuration block), plus a stale /health → / fix (no /health endpoint exists in main.py; confirmed via grep).

This is the hummingbot-api-side counterpart to hummingbot/condor#213, which does the equivalent (127.0.0.1 bind + tailscale serve) for Condor's own web dashboard.

Test plan

• docker compose config -q — valid, hummingbot-api:8000 defaults to 0.0.0.0 (unchanged), Postgres/EMQX resolve to 127.0.0.1
• API_BIND_HOST=127.0.0.1 docker compose config — confirms the override binds hummingbot-api:8000 to loopback
• docker compose -f docker-compose.yml -f docker-compose.tailscale.yml config -q — valid with the sidecar overlay + TS_SERVE_CONFIG mount
• bash -n setup.sh — syntax check passes
• make -n tailscale-status — Makefile syntax check passes
• pre-commit hooks (detect-private-key, detect-wallet-private-keys) pass
• Manual smoke test on a real Tailscale-enabled deploy: confirm tailscale serve status shows port 8000 forwarded and the API is reachable at http://hummingbot-api:8000 from another tailnet device while nmap/curl from outside the tailnet times out on all of 8000/5432/1883/etc. (not testable from this dev environment — no live tailnet/second machine available)

🤖 Generated with Claude Code

[greptile-apps]

Greptile Summary

The PR binds PostgreSQL and EMQX host ports to loopback, adds Tailscale Serve forwarding for the API, and introduces deployment diagnostics.

• Makes the API host bind configurable through API_BIND_HOST.
• Adds a Tailscale sidecar Serve configuration forwarding tailnet port 8000 to the loopback API.
• Adds make doctor checks for configuration, containers, port exposure, Tailscale, authentication, and API reachability.
• Updates setup prompts, credential handling, status commands, and deployment documentation.

Confidence Score: 3/5

The PR is not yet safe to merge because upgraded Tailscale deployments can still leave the trading API reachable through public interfaces.

Existing .env files bypass the only code that writes the loopback bind, while make deploy applies the Tailscale overlay without enforcing that value and Compose defaults the API mapping to 0.0.0.0.

Files Needing Attention: docker-compose.yml, setup.sh, Makefile

Important Files Changed

Filename	Overview
docker-compose.yml	Adds configurable API binding and loopback-only PostgreSQL/EMQX ports, but the API fallback remains public when older Tailscale configurations lack the new variable.
setup.sh	Fresh installations receive the appropriate API bind host, while the existing-configuration early exit leaves older Tailscale installations unchanged.
docker-compose.tailscale.yml	Adds the host-network Tailscale sidecar Serve configuration and mounts its static forwarding configuration.
tailscale-serve.json	Forwards tailnet TCP port 8000 to the API's loopback listener.
doctor.sh	Adds read-only diagnostics that detect insecure Tailscale binding and other deployment problems, but does not gate deployment.
Makefile	Adds diagnostics and Serve status reporting, while the deploy target still does not enforce the Tailscale-only API bind.
README.md	Documents the revised local and Tailscale exposure model and operational diagnostics.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  Public[Public interfaces] -. blocked when loopback bind is active .-> API[API port 8000]
  Tailnet[Tailscale device] --> Serve[Tailscale Serve :8000]
  Serve --> Loopback[127.0.0.1:8000]
  Loopback --> API
  API --> Network[emqx-bridge]
  Network --> EMQX[EMQX]
  Network --> Postgres[PostgreSQL]

Loading

_{Reviews (4): Last reviewed commit: "Setup: mask the password prompts, stop h..." | Re-trigger Greptile}