Operations

Remote Access

Choose between a private VPN, an HTTPS reverse proxy, and direct exposure.

ScenarioSolutionPublic Exposure
Personal use or small teamTailscale / Private VPNNone
Managed public domainHTTPS reverse proxy + NasDash authenticationPort 443 only
Port 2504 directly on the InternetNot recommendedPublic application port

For Tailscale, install the client on the NasDash host and the authorized devices, apply ACLs, and then open http://IP_TAILSCALE:2504. The Tailscale widget is independent of this access method: see the three Tailscale use cases.

For a domain, place NasDash behind a reverse proxy, enable HTTPS, maintain strong passwords, and restrict administration to trusted users.

Public does not mean unprotected

Public reader mode exposes authorized resources to anyone who can reach the instance. Verify categories, IPs, ports, calendars, and Docker hosts before enabling it.

For request rate limits, forwarded client addresses are ignored by default. Set NASDASH_TRUST_PROXY=true only behind a trusted reverse proxy that overwrites client-supplied forwarding headers and prevents direct access to NasDash. Otherwise keep NASDASH_TRUST_PROXY=false. This setting changes quota identity only; it does not change HTTPS detection or authentication cookie behaviour. Failed-login limits also apply per account, independently of forwarding headers.