mirror of
https://github.com/fosrl/pangolin.git
synced 2026-07-18 07:34:42 -05:00
[GH-ISSUE #571] Unable to ping from Newt or Wireguard install #12315
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 @mellow65 on GitHub (Apr 23, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/571
I have installed pangolin via the script from your website on a fresh install of deb 12 on my VPS. Everything starts up normal and I don't have any errors in the logs. When I try to start set up my first
When I use the newt script given, it pings and fails for ever.
I've tried using the docker install of newt, once it's up I still can't ping the ip of the WG on pangolin.
I've tried using a wireguard config file on a linux install, and still could not ping the ip of the WG on pangolin.
I've tried using a wireguard configuration on my windows computer, and it repeatedly tried sending a handshake initiation to peer 1.
I'm kind of out of things to try at this point. I would love some extra trouble shooting ideas.
VPS: DEB12 install via script
Home server: installed via script from pangolin
Aaand as I was just wrapping this up, I figured out why it wouldn't connect. The proxy service from cloudflare on the pangolin.mywebsite.com was somehow killing the connection. I'm going to use the word "somehow" as I barely understand most of this stuff works, but I'm pretty ok at breaking things and flipping the switches until I figure out what's wrong.
Any thought on how to keep the cloudflare proxy service working? It seems like another small layer of not exposing my IP address.
Also another question related to the newt install, if I'm using the script provided by the web GUI, it seems to stay running taking up my terminal screen, and if I control C out of that, it clearly kills my connection. Is there any future plan to work in the option to keep it running with the systemd service automatically?
@tannkosten commented on GitHub (Apr 23, 2025):
Hello
Cloudflare Proxy is for HTTP/HTTPS traffic mostly
You can read about the ports they support here: https://developers.cloudflare.com/fundamentals/reference/network-ports/
As you can see, port 51820 is not listed there.
When it comes to running the Newt container, you can add a -d flag to your command (docker run -d). You can also go the docker-compose.yml file route, and run it with
docker compose up -ddocker-compose.yml example:
@mellow65 commented on GitHub (Apr 23, 2025):
Ah yes, that makes sense on the cloudflare, thank you for the info!
And my comment about Newt wasn't about running it in docker, but the cli command. Like I understand what needs to happen, I need to set up a systemd service to run it all the time, but I missed that the first few times I was playing around. I was just curious if that at some point was going to be baked into the command that's generated when making a new site. Or potently on the same page that has the CLI command also include the steps to make it a permanent install. Food for thought.
I'm excited to play around with this!!!