@BreadAndCircuits I use Pangolin on a VPS for remote access to my HomeLab.
Homelab
Rules
- Be Civil.
- Post about your homelab, discussion of your homelab, questions you may have, or general discussion about transition your skill from the homelab to the workplace.
- No memes or potato images.
- We love detailed homelab builds, especially network diagrams!
- Report any posts that you feel should be brought to our attention.
- Please no shitposting or blogspam.
- No Referral Linking.
- Keep piracy discussion off of this community
How do you like it? Care to describe your setup a bit?
@BreadAndCircuits sure
I like it because it's just me and one cheap VPS to run Pangolin so no 3rd party services. That creates a Wiregaurd tunnel to Newt. It handles dynamic IP/CGNAT, https certificates, SSO with per user access control to services and I can ssh in using it. I have one Proxmox VE and one Proxmox PBS node. The first had HAOS VM and a Docker VM which runs Newt and Portainer under Docker Compose. Proxmox VE makes setting up containers easy by providing helper scripts.
Pangolin's default docker-compose ships its own Traefik container, and that's almost always what's actually fighting your existing one, not a config typo on your end. Two ways out of it that I've seen work:
- Comment out the traefik service in Pangolin's compose file entirely and let your existing traefik instance handle routing via labels. Pangolin's docs have a section for using an existing reverse proxy that walks through pointing your own traefik at Gerbil's exposed port instead of the bundled one.
- Or the reverse: let Pangolin's traefik own ports 80/443 and demote your main one to a different port/internal-only role if it's not doing much else.
First option is cleaner if your main traefik is already handling other services and you don't want two separate ACME/cert setups running side by side.
Hum, I guess that's exactly what's going on. I need to check the docs again. Thanks for the tip!