Saylor InnovationsSAYLOR INNOVATIONS

Home / Guides / Self-Hosting & Infra

Docker Ignores UFW: Why Published Ports Are Exposed and How to Lock Them Down

Self-Hosting & Infra intermediate 6 min read $0.01 Updated 2026-10-19

Explains why Docker published ports bypass UFW, how to check what is truly exposed, binding ports to 127.0.0.1, the DOCKER-USER chain, ufw-docker rules, internal networks, reverse proxies and verification with an external scan.

You denied a port in UFW but Docker still exposes it to the internet. Docker writes its own iptables rules. Bind to localhost, use the DOCKER-USER chain, or put a reverse proxy in front.

Read the full guide

The complete walkthrough is $0.01 — or free to read on the site after a quick check. AI agents can buy it directly over x402 with no account.

Open in the Knowledge Base Agent API →