mirror of
https://github.com/fosrl/pangolin.git
synced 2026-05-21 09:21:15 -05:00
[GH-ISSUE #187] Trouble tunneling from VPS to 1 of 2 home servers #1330
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/pangolin#1330
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @reneald on GitHub (Feb 11, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/187
I'm having some troubles getting Pangolin to work on my environment. I fired up a VPS on Hetzner and deployed Pangolin there. Opened ports 80, 443 and UDP 51820. I've created an A record for my domain pointing to the public IP of my VPS. (As a sidenote, I had an A record in my DNS pointing to my home public IP address, but removed that when I added the one pointing to my VPS.)
I can access the pangolin management interface on https://pangolin.MYDOMAIN.COM. So far, so good.
I have 2 servers in my homelab (let's say server-01 and server-02). Both are running ubuntu with several docker services. I added 2 sites in Pangolin, one for each server, and started a newt docker container on each server as described in the docs. Both show up as Online in Pangolin. But only server-01 works: I can expose docker services on that server through Pangolin, but any service I try to expose from server-02 fails. The only difference that I can see is that I used to have some (but not all) services on server-01 exposed via SWAG, and none on server-02. But I don't see how that could make a difference.
The newt container logs on server-02 just show
Error connecting to target: dial tcp 172.22.0.2:25600: connect: connection timed out.Is there anything I can do to troubleshoot this? Happy to provide more specific information if that helps.
[edit: I had some more problems listed here which occurred on server-01, but I've been able to solve those already]
@reneald commented on GitHub (Feb 11, 2025):
Closing this issue: apparently I only need a newt container on one of my servers, and can just point the resources to the IP of the other server. I incorrectly assumed that I would need a site for each server.
@yarafie commented on GitHub (Apr 23, 2025):
@reneald
Hi. Sorry to jump in but I was looking at pangolin and it kind of intrigued me.
I'm currently using swag as a reverse proxy with my domain registetered on cloudflare with dynamic dns updating the A Records in cloudflare. It works fine no issues, but like I said pangolin intrigued me to try something new.
So are you still using swag or have you replaced it with pangolin completly?
@reneald commented on GitHub (Apr 23, 2025):
@yarafie I've completely migrated to pangolin and can't imagine going back to swag.
@yarafie commented on GitHub (Apr 23, 2025):
Thanks.
So you completly switched over to pangolin one shot, or did you run swag and pangolin in parallel for a short while until you migrated over everything to pangolin?
@reneald commented on GitHub (Apr 23, 2025):
I completely shut down swag in one go. I'm not aware of a way to point my domain name to both the VPS that pangolin runs on, and my home server where swag used to live. I have nobody else depending on my server so I just decided to give pangolin a go. I figured that I could very easily fire up swag again if need be, but pangolin just worked 🙂
@yarafie commented on GitHub (Apr 23, 2025):
Thanks.
So you were running swag on your home server and now pangolin on a VPS cloudserver not on your home server?
Just about to do the same and before I jump in head first, thought I'd see who else may have migrated from swag to pangolin.
@reneald commented on GitHub (Apr 23, 2025):
Exactly that. The pangolin installation guide made the whole process pretty painless.