Insights
Unraid remote access: choose the right path
Compare Unraid remote access methods, understand Connect's public WebGUI exposure, and check access to your apps and files.

On this page
You can access Unraid remotely through its official Tailscale integrationOpens in a new tab, a WireGuard tunnelOpens in a new tab or Unraid Connect Remote Access. For remote administration, Unraid recommends Tailscale because it avoids exposing the WebGUI, your server's browser-based management interface, to the public internet.
In short:
- Personal administration. Use Tailscale to reach the WebGUI without making it public.
- Apps and files. Use a tunnel configured for the containers or network drives you need.
- Public browser access. Connect Remote Access publishes the WebGUI through router port forwarding, separate from dashboard sign-in.
Choose access for the services you need
Compare the methods by what you need to reach and what you must configure.
| Access method | Intended access | Public WebGUI | Setup needed |
|---|---|---|---|
| Official Tailscale integration | Administration and configured resources | Not required | Device access and resource configuration |
| Unraid WireGuard tunnel | Administration, apps and files | Not required | Tunnel and resource configuration |
| Connect Remote Access | Browser-based administration | Exposed when enabled | Remote Access and router forwarding |
WireGuard is a tunnel protocol embedded in Unraid, while Tailscale is an integrated networking product. A virtual private network (VPN) tunnel connects your remote device to a private network, but its configuration controls which resources you can reach. Choose Tailscale for personal administration from an authorized device. Keep WireGuard as an option if you want to configure a tunnel yourself.
Connect is a management service with a separate Remote Access feature. Its dashboard uses a server-initiated connection with restricted application programming interface (API) access for supported features. Signing in doesn't enable full WebGUI access. Choose Connect Remote Access only when you specifically need its public-facing WebGUI URL, not as a substitute for configured access to apps or files.
Get your private access path ready
Change only devices you own or administer. Save the current settings and keep local access available so you can recover if a change breaks access.
1. Identify the services you need.
List the WebGUI, container apps and network drives you want to reach. Don't assume one working connection covers every item.
2. Confirm local access.
Open each intended service from your home network. If it doesn't work locally, address that before adding remote access.
3. Update and protect Unraid.
Update Unraid and use a strong, unique root password before enabling remote access.
4. Configure your chosen route.
Follow Unraid's official guidance for the Tailscale integration or its embedded WireGuard tunnel. Configure the path for your listed resources, then check your account's permissions. Network reachability and permission to use a service are separate checks.
Check your version before following a guide
For Unraid 7.2.x, the current remote-access documentation states:
Dynamic, on-demand remote access is not currently exposed in the Unraid API settings page. If you need remote management without keeping the WebGUI exposed through port forwarding, prefer Tailscale or another VPN Tunnel.
The Connect product pageOpens in a new tab and older remote-access documentationOpens in a new tab describe dynamic access that opens access on demand. The current documentation instead describes Always or Disabled, with Static or UPnP forwarding. If your interface shows only Always and Disabled, don't look for a missing dynamic toggle or assume an automatic time limit.
WAN means wide area network, here the internet-facing side of your router. UPnP means Universal Plug and Play, which can let software request router forwarding automatically. Static describes how the forwarding rule is created, not a promise that access closes automatically.
Check access before you leave home
Have your chosen method, Unraid version, service list and authorized remote device ready. Test only your own or authorized services, and keep local access plus saved settings available for recovery.
1. Check the local baseline.
Confirm that each intended service still works from your home network. A successful check shows that the service is available locally. If it fails, fix local access first.
2. Connect from a separate network.
Use your authorized remote device outside your home network and connect through your chosen access path. For Tailscale or WireGuard, check that the private connection is active before opening the intended service.
3. Test each required service.
Open the WebGUI, each needed container app and each needed file share separately. Check that you can perform the intended action with your account. A working WebGUI proves management access through that path, not access to every app or share.
4. Keep dashboard access separate.
If the Connect dashboard works but the WebGUI doesn't, record that as dashboard access only. Dashboard visibility doesn't pass your WebGUI or file-access check.
5. Record failures before changing settings.
Note your Unraid version, access method, failing service and any error shown. If local access works but remote access fails, check the chosen connection and intended resource before changing server settings.
Strict mode for Secure Sockets Layer/Transport Layer Security (SSL/TLS) requires clients to resolve your server's Domain Name System (DNS) name. An internet outage can then make the WebGUI unavailable, so don't assume local access will always survive. Don't ignore certificate warnings to regain access.
Your check passes when the authorized remote device reaches each intended service through the chosen path. That proves access at the time of the check, not continuous availability, other users' permissions or recovery from a powered-off server.
Where doxx.net fits. doxx.net offers direct device-to-device connections and full, unmodified file transfer between devices, but those capabilities don't establish support for mounting Unraid shares. To try them for private device communication, create a doxx.net account, download the app and connect a device to the private networkOpens in a new tab.