Documentation Index
Fetch the complete documentation index at: https://mintlify.com/Crosstalk-Solutions/project-nomad/llms.txt
Use this file to discover all available pages before exploring further.
Default behavior
By default, N.O.M.A.D. listens on all network interfaces. Anyone on the same local network as your server can access the Command Center athttp://SERVER_IP:8080 and Dozzle at http://SERVER_IP:9999.
This is intentional for the common use case: a home or classroom LAN where all connected devices should have access. On a private, trusted network, no additional configuration is needed.
When to restrict access
Consider restricting access if:- Your server is connected to a shared or semi-public network (office, apartment building, campus Wi-Fi)
- You want only specific devices to reach N.O.M.A.D.
- You are running N.O.M.A.D. on a machine that is reachable from outside your local network
Restricting access with ufw (Ubuntu)
ufw (Uncomplicated Firewall) is the standard firewall tool on Ubuntu. Use it to allow specific IP addresses or subnets while blocking others.
Allow access from a specific IP only
Allow access from a subnet
Enable ufw if not already active
ufw rules are evaluated in order. Place allow rules before deny rules for the same port, or the deny rule will block all traffic regardless of source.Private network (trusted LAN)
If your server is on a private home or office network with only trusted devices, no firewall configuration is required. The default setup works as intended — all devices on the LAN can access N.O.M.A.D.Shared or semi-public network
If you cannot guarantee that all devices on the network are trusted:- Use
ufwto restrict ports 8080 and 9999 to specific IP addresses or a trusted subnet - Consider placing N.O.M.A.D. on a dedicated VLAN with controlled access
- If you need access from outside the local network, set up a VPN (WireGuard, Tailscale) rather than exposing ports publicly