Sign inRequest DemoTry for free

Home Labs

Set up Twingate on your home lab to access self-hosted services from anywhere.

These guides walk you through setting up Twingate on common home lab platforms so you can access your self-hosted services remotely without port forwarding, dynamic DNS, or a VPN server.


Getting Started

The setup takes about 15 minutes regardless of which platform you’re running:

  • Sign up for a free Twingate account at twingate.com. The Starter plan covers most home lab setups.
  • Create a Remote Network in the Admin Console to represent your home network.
  • Deploy a Connector on your home lab. Most platforms below have a native add-on or container. If yours doesn’t, the Docker Compose guide works on anything that runs Docker.
  • Create Resources for the services you want to access remotely. Add each service by its local IP address and port, such as 192.168.1.50:8123 for Home Assistant or 192.168.1.100:32400 for Plex.
  • Install the Twingate Client on your phone, laptop, or tablet. Open the Client, sign in, and your home lab Resources show up automatically.

That’s it. No port forwarding, no dynamic DNS, no VPN server to maintain.

Home Server Platforms

Home Assistant

The Home Assistant Getting Started guide walks through installing the Twingate add-on from the Home Assistant Add-on Store. Once installed, you can access your dashboard, automations, and any devices on your network remotely.

Proxmox

The Getting Started with Proxmox guide covers deploying a Connector on your Proxmox host using the helper script.

Unraid

The Unraid Getting Started guide covers installing the Twingate Connector from the Unraid Community Apps store. From there you can access your Unraid dashboard, Docker containers, and VMs remotely.

ZimaOS

The ZimaOS Getting Started guide walks through deploying Twingate on ZimaOS devices, including ZimaBoard and ZimaCube hardware.

CasaOS

The CasaOS Getting Started guide covers installing the Twingate Connector on CasaOS and accessing your self-hosted apps from outside your home network.

NAS Devices

Synology

The Synology NAS guide walks through setting up Twingate on Synology devices running DSM 7, using the Docker package to run the Connector directly on your NAS.

QNAP

The QNAP NAS guide covers deploying the Twingate Connector on a QNAP NAS using Container Station.

TrueNAS SCALE

The TrueNAS SCALE guide covers running the Connector as a container on TrueNAS SCALE so you can access your pools, shares, and apps remotely.

Troubleshooting

If something isn’t working, here are the most common issues:

  • Can’t reach a service after setup: Make sure the Twingate Client is running on your device and you’re signed in. Check that the Resource IP address and port match what the service actually listens on. A quick test: can you reach the service from another device on the same local network?
  • Connector shows as offline: Verify the container or add-on is running on your home lab platform. Check that your home network has internet access and isn’t blocking outbound connections on port 443.
  • Slow performance: Twingate establishes peer-to-peer connections when possible, which keeps latency low. If connections feel slow, check your home network’s upload speed, as that’s typically the bottleneck for remote access.
  • DNS issues: If you’re using local DNS names (like nas.local) instead of IP addresses, make sure the Connector can resolve them. Using IP addresses directly avoids local DNS resolution issues in most home lab setups.

For more help, see the Twingate Troubleshooting Guide.

Further Help

The Twingate community on Reddit is full of home lab folks who have been through this. Drop by to ask questions or see what other people are running.

Last updated 15 minutes ago