v1.17.0 upgrade shows "no available server" message for local sites #2

New Issue

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

MrUnknownDE commented

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

Originally created by @gitmotion on 4/4/2026

Describe the Bug

After upgrading to v1.17.0, I was getting a no available server message when accessing a local site resource.

this was happening only on Local sites (newt sites were fine)
- this was also happening on another pangolin instance i upgraded

Workaround:

after noticing the above, i tried creating a new local site and switching a resource to the new site and it started working again
so moved all my previous local sites to the new local site, removed the old one, and it was all working again.

Not exactly sure what happened, but my guess would be a potential migration issue for local sites??

seeing that creating a new local site and switching a resource to it fixes the issue, seems like creating a new local site corrects the info needed for the v1.17.0 upgrade

Just thought I'd mention this in case and if anyone else ran into the same issue for local sites

Thanks!

Environment

OS Type & Version: Debian GNU/Linux 13 (trixie)
Pangolin Version: 1.17.0
Gerbil Version: 1.3.1
Traefik Version: 3.6.12
Newt Version: v1.10.3 & v1.11.0 newt sites work fine
Olm Version: n/a

To Reproduce

Upgrade to 1.17.0 and access a local site

Expected Behavior

Upgrading to 1.17.0 should direct to local sites correctly

*Originally created by @gitmotion on 4/4/2026* ### Describe the Bug After upgrading to `v1.17.0`, I was getting a `no available server` message when accessing a `local` site resource. - this was happening only on `Local` sites (newt sites were fine) - this was also happening on another pangolin instance i upgraded Workaround: - after noticing the above, i tried creating a new local site and switching a resource to the new site and it started working again - so moved all my previous local sites to the new local site, removed the old one, and it was all working again. Not exactly sure what happened, but my guess would be a potential migration issue for local sites?? - seeing that creating a new local site and switching a resource to it fixes the issue, seems like creating a new local site corrects the info needed for the `v1.17.0` upgrade Just thought I'd mention this in case and if anyone else ran into the same issue for local sites Thanks! --- ### Environment - OS Type & Version: Debian GNU/Linux 13 (trixie) - Pangolin Version: 1.17.0 - Gerbil Version: 1.3.1 - Traefik Version: 3.6.12 - Newt Version: v1.10.3 & v1.11.0 newt sites work fine - Olm Version: n/a --- ### To Reproduce Upgrade to 1.17.0 and access a local site --- ### Expected Behavior Upgrading to 1.17.0 should direct to local sites correctly

MrUnknownDE closed this issue

2026-04-05 17:00:31 +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#2