Awesome, good to hear. Just a reminder that I forgot when I sent that link: double-check the Tutorial, it might have slightly outdated information. But a few lessons I learned when setting it up:

Pangolin uses its own auth. You can use a OIDC provider if you like, but you have to set it up. I use TinyAuth in conjunction because I have so few users.

To bypass auth on Pangolin, you must disable it and it will appear “Unprotected”. This helps with mobile apps, which don’t know how to deal with third-party login screens, but it leaves the login screen of whatever server you’re running (like Jellyfin) accessible by everyone. So something more hardened as your OIDC provider at the frontend help. Although lots of apps, again like Jellyfin, don’t have native OIDC login.

The solution would be to route it with Private Resources, which are zero-trust connections. Great for a few people on your network, but it requires you setting up the Client app to access the Pangolin network. I’ve had issues with DNS on Android before, but your problems may vary.

If you have any more questions, let me know. I’ve been using Pangolin for only about a year, but I think I learned enough to help.

Sure, https://pimylifeup.com/pangolin-linux/

But I have to say, the Pangolin Docs are quite good as well: https://docs.pangolin.net/self-host/quick-install

I use Pangolin on a kinda cheap VPS on Hetzner (they’re now a bit too pricey), and route my services through Site Connectors (Newt, it’s called). Dealing with opening my firewall is a pain I don’t wanna think about, but Pangolin creates a websocket and can do NAT traversal from the Site Connector, so no swiss-cheesing your firewall.

It’s nice because you can contain different services with VLANs to further segment and protect your network, and each Site Connector can work for many services (if there’s no firewall rules restricting it/VLANs) or you can put a Site Connector on each server individually, if segmentation is important to you.