Repository navigation
v1.4.1 — Firewall guidance for console & exit nodes
Documentation and landing update
This release is documentation-only — no API, database, or console behaviour changed.
- README firewall matrix clarified. The console-host table now says port 53 is console-only, and a dedicated Exit node ports table documents what a node actually needs:
51820/udpinbound (or the custom WireGuard port) for peers443/tcpoutbound for the agent's console polling53/udp+tcpoutbound only when peers use the console's AdGuard resolver22/tcpinbound for the one-time install only
- Exit nodes do not need inbound 80/443. Cloud-firewall guidance now distinguishes console-host rules from node rules and calls out node egress on 443.
- New landing Firewall section at
/#firewall, with console-host and exit-node port cards, inbound/outbound/internal labels, the private3000/tcpwarning, and cloud-firewall guidance. - Navigation: Firewall added to the header/mobile navigation and footer.
Upgrade notes
- No migrations, configuration changes, or restarts are required for the application itself.
- If you self-host the landing site, redeploy it to publish the new
/#firewallsection.
Verification
landing: tsc --noEmitclean.landing: next buildclean (10/10 static pages generated).- README and landing content reviewed for consistent console-host vs exit-node port guidance.