wintermelons / homelab

Configuration of my home servers.
MIT License
0 stars 0 forks source link

Best way to open the servers to the internet: DDNS or tunnel or vpn? #3

Open fshrr opened 1 day ago

fshrr commented 1 day ago

There are multiple ways of giving access to our local resources to the internet. Main three being DDNS+exposed ports, tunnels or private vpns. Here are some of the pros and cons and points to remember for each.

DDNS+exposed port

Expose a port from the local network allowing outside traffic to hit the external IP directly. Using DDNS with cloudflare-ddns allows us to update dns records on for a domain when ISP changes our external IP.

pros

cons

Points to note

Tunnels (cloudflare tunnel+cloudflare access, ngrok)

Use something like cloudflare tunnel where users make a request to cloudflare's data centres. Cloudflared daemon is installed on the server to keep a persistent https outbond tunnel open with cloudflare. The data is transferred between this tunntel. Cloudflare access is a complementary service used to authenticate any users.

pros

cons

Private vpns (wireguard, tailscale, netbird)

The server and all devices making requests to the server are inside a vpn. Wireguard can be implemented on its own. There are services like tailscale that set up mesh vpn with zero config. Unlike tailscale, netbird offers self hosted solution.

pros

cons

fshrr commented 1 day ago

Currently leaning towards ddns or netbird. But researching more