Port forwarding is the oldest way to expose a home server, and the one that most often goes wrong. Pangolin skips it entirely: a small public VPS acts as the front door, and your home network connects outward to it through an encrypted tunnel.

What Pangolin Actually Does
Pangolin is an open-source, self-hosted reverse proxy with tunneling and identity-aware access control built in. You run the Pangolin server on a VPS with a public IP address. Services at home, in a lab, or at another office connect to that server over WireGuard tunnels, so nothing needs to be opened on the router at the remote site. Visitors hit your domain, Pangolin checks who they are, and traffic travels down the tunnel to the right internal service.
The stack is made of four parts. Pangolin itself provides the dashboard and API. Gerbil manages the WireGuard interface on the server. Traefik handles HTTP routing and TLS certificates. Newt is the small agent that runs at the remote site and dials home to the server. If you have used Cloudflare Tunnel, the concept will feel familiar, except the server, the certificates, and the user database all live on hardware you control.
The tunnel design solves a problem that port forwarding cannot. Many home connections sit behind carrier-grade NAT, which means there is no public address to forward to at all. Because Newt only makes outbound connections, that limitation stops mattering.
Before you start, gather a few things. You need a Linux VPS with Docker installed and a domain name you can edit DNS for. Open TCP ports 80 and 443 and UDP port 51820 in the VPS firewall. Newer releases also use UDP port 21820 for client connections, so check the current documentation for the exact list. Have a real email address ready too, since Let’s Encrypt uses it for certificate notices.
Installing the Server and Connecting a Site
Start with DNS, because certificates will fail if records have not propagated. Create an A record for your base domain pointing at the VPS address. Then add a wildcard A record, *.example.com, pointing to the same address. The wildcard is what lets each published app get its own subdomain without a new DNS entry every time. The dashboard itself usually lives on a subdomain such as pangolin.example.com, which the wildcard covers.
Next, SSH into the VPS and download the Pangolin installer using the command shown in the official documentation, then run it with sudo. The installer asks a short series of questions: your base domain, the dashboard domain, the email address for Let’s Encrypt, and whether to enable Gerbil tunneling. Say yes to tunneling, since that is the whole point of this setup. It can also configure SMTP for email-based features, which you can skip and add later. When the prompts finish, it writes a config directory containing the Docker Compose file, Traefik settings, and Pangolin’s config, then offers to start the containers.
Open the dashboard domain in a browser to finish setup. Depending on the version you installed, you may need a setup token that the server prints in its container logs before you can create the first admin account. After that, create an organization and head to Sites, then add a new site and choose the Newt option. The dashboard displays an ID, a secret, and the endpoint URL. Copy the secret immediately, because it is shown only once.

On the machine at home, run Newt. The Docker route is the tidiest: add a service using the fosrl/newt image and pass the endpoint, ID, and secret as environment variables, or run the binary with –id, –secret, and –endpoint flags. Within a few seconds the site should flip to online in the dashboard. If it stays offline, the usual culprits are a blocked UDP port on the VPS firewall or a typo in the endpoint URL.
Now publish something. Open Resources, add a new HTTPS resource, give it a name, pick a subdomain on your base domain, and select the site you just connected. For the target, enter the internal address and port of the service as Newt sees it. This detail is easy to miss: the target does not have to be the machine running Newt, because the agent can reach anything on its local network. A NAS, a Home Assistant box, and a Jellyfin server can all sit behind one Newt instance. Pangolin turns its own authentication on for new resources by default, so visitors hit a login screen before they ever touch your app. You can use SSO accounts, a shared password, a PIN, or one-time email codes, and you can whitelist specific addresses.
Locking It Down and Knowing the Limits
Pangolin’s login screen in front of an app is a real security layer, but it can collide with software that expects to talk to its own server directly. Mobile apps, webhooks, and API clients cannot complete a browser login. For those, Pangolin lets you relax authentication on a resource or add bypass rules for specific paths. Use that sparingly, and only for apps that carry their own strong login. Also remember that the VPS is now your single front door: keep the OS patched, restrict SSH to keys, and back up the config directory, since it holds the database and certificates.

Pangolin also supports raw TCP and UDP resources for things like game servers or SSH, though those require extra port mappings on the VPS and a closer read of the docs. If what you want is private access to your whole home network rather than public web apps, a mesh VPN such as Netbird may suit you better. The two solve different problems, and plenty of setups run both. So before you publish your tenth service, ask which of them actually needs to be reachable from the open internet.
Frequently Asked Questions
Do I need to open ports on my home router to use Pangolin?
No. The Newt agent at home makes only outbound connections to your VPS, so the remote network needs no inbound port forwarding.
What do I need before installing Pangolin?
You need a Linux VPS with a public IP and Docker, a domain with A and wildcard DNS records, and open TCP 80/443 and UDP 51820 ports.
Can Pangolin protect apps with a login page?
Yes. Resources can require SSO, a password, a PIN, or one-time email codes, and you can whitelist specific users.





