Pangolin Can’t Ping Sites #503

New Issue

MrUnknownDE · 2026-04-05T17:13:32+02:00

MrUnknownDE commented

2026-04-05 17:13:32 +02:00

Originally created by @poyasyn on 12/12/2025

Describe the Bug

Hi! I’ve been trying to route resources to containers on Newt connected sites using both the assigned IP and container hostnames (after confirming Newt shared network with said containers) to no avail. I decided to ping the assigned IP but got 100% packet loss; only clue is the Newt logs displaying the WG error “context deadline exceeded.” On Pangolin’s end, however, the site health checks are marked as healthy all throughout. There are no firewall conflicts, port conflicts, etc. that would imply why the pings are failing.

Environment

OS Type & Version: Ubuntu 24.04
Pangolin Version: 1.13.0
Gerbil Version: 1.3.0
Traefik Version: 3.6
Newt Version: 1.7

To Reproduce

Create a fresh Pangolin install. Set up UFW in accordance with Pangolin’s documentation. Create a site using the docker compose format. Start up Newt compose on target VPS, UFW also configured to documentation and adjusted for Newt’s organically chosen port (2112 in this case). Site should show as healthy and functional. Create a resource pointed at a known to be functional and accessible, it should show as 404 or timeout when assigned URL is attempted. Pinging assigned IP loses all packets.

Expected Behavior

Resource URL points to site resource and Pangolin VPS can ping Newt connected sites using its assigned IP.

*Originally created by @poyasyn on 12/12/2025* ### Describe the Bug Hi! I’ve been trying to route resources to containers on Newt connected sites using both the assigned IP and container hostnames (after confirming Newt shared network with said containers) to no avail. I decided to ping the assigned IP but got 100% packet loss; only clue is the Newt logs displaying the WG error “context deadline exceeded.” On Pangolin’s end, however, the site health checks are marked as healthy all throughout. There are no firewall conflicts, port conflicts, etc. that would imply why the pings are failing. ### Environment - OS Type & Version: Ubuntu 24.04 - Pangolin Version: 1.13.0 - Gerbil Version: 1.3.0 - Traefik Version: 3.6 - Newt Version: 1.7 ### To Reproduce Create a fresh Pangolin install. Set up UFW in accordance with Pangolin’s documentation. Create a site using the docker compose format. Start up Newt compose on target VPS, UFW also configured to documentation and adjusted for Newt’s organically chosen port (2112 in this case). Site should show as healthy and functional. Create a resource pointed at a known to be functional and accessible, it should show as 404 or timeout when assigned URL is attempted. Pinging assigned IP loses all packets. ### Expected Behavior Resource URL points to site resource and Pangolin VPS can ping Newt connected sites using its assigned IP.

MrUnknownDE closed this issue

2026-04-05 17:13:32 +02:00

MrUnknownDE added the stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale labels 2026-04-05 17:13:33 +02:00

Sign in to join this conversation.

Branches Tags

main

dev

dependabot/npm_and_yarn/dev-minor-updates-b4e5d6b9c5

revert-2766-feature/systemd-install-instructions

dependabot/npm_and_yarn/prod-patch-updates-05702d39f2

dependabot/npm_and_yarn/next-16.2.1

dependabot/npm_and_yarn/recharts-3.8.1

alerting-rules

private-site-ha

dependabot/docker/docker/library/node-25-slim

ssh

delete-account

msg-delivery

org-only-idp

cicd

patch

site-targets-auto-login

No Label stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale stale

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/pangolin#503