TunnelNet Guides

Host a website from home on your own IP address

2026-11-19

Running a small website from a computer at home is easy to start and hard to finish, because the last step is letting the internet in. If your provider shares one address between many customers (CGNAT) or your router will not forward ports, nothing from outside can reach your computer. This page shows a setup that works anyway, with what we actually ran and what we did not.

Tested on

Lab run on 18 November 2026: a Debian 12 virtual machine behind a NAT router with no port forwarding, Docker Engine 29.10.0 with Docker Compose v5.8.0, and the normal TunnelNet installer on an internal test account. A test machine in Atlanta played the visitor. We used http only; we did not test https, a domain name or certificates.

The idea

Give the computer a public address that does not depend on your router or provider, then put one small web server in front as the "front door" that sends visitors to your site. TunnelNet IP gives the address: your computer keeps a tunnel out to us and we route the address down it, so nothing has to be forwarded at home.

1. Install and check the address

Run the installer from your TunnelNet dashboard. When it finishes, your machine has a public address and nothing is open yet:

$ sudo tnet ports
Mode: filtered
  (no rules)

2. One front door

We used Caddy in a container as the front door, with the site behind it. The front door listens on port 80 and sends each path to the right place. Our full compose file and Caddyfile, with real output, are in A public IP for a Docker host behind CGNAT. The point is that only the front door publishes a port. Your site and anything else stay private behind it.

3. Open the port and test from outside

$ sudo tnet ports allow tcp 80 --note=front-door
Allowed tcp 80

It can take up to a minute to start answering. From the visitor machine, the page loaded. Before this step the same request timed out after 8 seconds, because nothing from outside could reach the home line.

4. Check that it comes back after a reboot

We rebooted the host. The tunnel starts at boot and Docker restarted the containers because of restart: unless-stopped. Our test answered again 44 seconds after the reboot command, with the same address and the same open port.

5. Close it again

$ sudo tnet ports deny 80
Denied port 80

It stopped answering 13 seconds later.

What we did not test

  • https. Caddy can fetch a certificate by itself once a domain points at your address, but we did not run that here. Do not put passwords or private data on a plain http page.
  • A domain name. You would add a record for your domain that points to the TunnelNet address. We did not test that part.
  • Heavy traffic. 1 TB a month is included, then your speed drops to 10 Mbit/s until the 1st; an extra 1 TB is $15.

Good to know

  • Other ports stay closed until you run tnet ports allow.
  • Your site will see visitors as coming from TunnelNet, not from their own address. That matters if you rely on visitor addresses for logs or limits.
  • Outgoing mail on port 25 is blocked.
  • There is no uptime guarantee yet, so do not host something that cannot be down for a few minutes.