Local resouce unavailable through "Local" site in 1.17.0 #7

New Issue

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

MrUnknownDE commented

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

Originally created by @yellowsnow3 on 4/4/2026

Describe the Bug

I have a docker container running at a local IP on the Pangolin VPS. I've used this docker container for months, but after updating to v1.17.0, the local site doesn't route traffic anymore. The error when trying to access the resource is "no available server" which I know from a failed health check. However, on the Local site there are no health checks I can configure. When I installed another newt container directly next to pangolin and switched to that site, the resource worked like it did in the months before. I assume something was changed on the local site health checks, because that would explain it not routing due to a failed health check.

Environment

OS Type & Version: Ubuntu Server 24.04.4 LTS
Pangolin, Gerbil, Traefik and Newt Version were updated to latest right after the 1.17.0 release

To Reproduce

Start a docker container on a local port (e.g. 172.17.0.1:3000) and add a resource through the standard Local site (without newt). When visiting the resource, it returns "no available server" even though the container is functional and can be pinged from inside the traefik container.

To workaround, install newt on the same machine where the container and pangolin are already running and change the site of the resource to this newt. Now it works!

Expected Behavior

Local resources should route traffic normally like they did previously. If health checks are involved, let the user edit/disable them, as they may cause errors.

*Originally created by @yellowsnow3 on 4/4/2026* ### Describe the Bug I have a docker container running at a local IP on the Pangolin VPS. I've used this docker container for months, but after updating to v1.17.0, the local site doesn't route traffic anymore. The error when trying to access the resource is "no available server" which I know from a failed health check. However, on the Local site there are no health checks I can configure. When I installed another newt container directly next to pangolin and switched to that site, the resource worked like it did in the months before. I assume something was changed on the local site health checks, because that would explain it not routing due to a failed health check. ### Environment - OS Type & Version: Ubuntu Server 24.04.4 LTS - Pangolin, Gerbil, Traefik and Newt Version were updated to latest right after the 1.17.0 release ### To Reproduce Start a docker container on a local port (e.g. 172.17.0.1:3000) and add a resource through the standard Local site (without newt). When visiting the resource, it returns "no available server" even though the container is functional and can be pinged from inside the traefik container. To workaround, install newt on the same machine where the container and pangolin are already running and change the site of the resource to this newt. Now it works! ### Expected Behavior Local resources should route traffic normally like they did previously. If health checks are involved, let the user edit/disable them, as they may cause errors.

MrUnknownDE closed this issue

2026-04-05 17:00:32 +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

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/pangolin#7