Huh, Pangolin seems pretty cool for the inadvisable hobby of hosting internet-exposed services from a homelab? I'd been doing this with an unholy combination of caddy, tailscale, and reverse ssh tunnels. This seems a lot easier?
Huh, Pangolin seems pretty cool for the inadvisable hobby of hosting internet-exposed services from a homelab? I'd been doing this with an unholy combination of caddy, tailscale, and reverse ssh tunnels. This seems a lot easier?
Got Pangolin running on one of my cheap cloud VMs in 10 minutes. Got a couple of my homelab servers talking to it in another 5 minutes. Had a site with an SSL cert from Let's Encrypt running in 30 seconds after that. I'm looking for the catch
@bitprophet I've been using tailscale + caddy for this, but nice thing about Pangolin is it's all-in-one and self-hosted with a web UI.
@skippy Yeah, the VPS just acts as a proxy relay basically, so double bandwidth. But, I'm not running anything particularly intensive over it. Anything like that, I'd just host totally in the cloud
@bitprophet Yeah, it's got traefik under the hood for the httpd along with wireguard for the proxy/VPN stuff
One thing I'm not quite so sure about with Pangolin is that it sticks the admin web UI out on the cloud VM. Outbound tunnel daemons connect to it from my homelab servers. Not a ton different, functionally, from using tailscale.
But, I'd rather have the cloud VM be as stupid as possible and get marching orders from a control node behind my firewall. I kind of had this when I was doing reverse tunnels with SSH, but I still had to configure the HTTP proxy stuff on the cloud VM.
Though one nice thing about the Pangolin frontend in the cloud is that it looks like I could use it as an SSO gateway with auth-related HTTP headers if I ever wanted to create user accounts and invite folks to use semi-private apps from my homelab