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 GitHub (Apr 4, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2788
### 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
@oschwartz10612 commented on GitHub (Apr 5, 2026):
Hello! I think this was fixed shortly after the release in https://github.com/fosrl/pangolin/issues/2782. Could you pull the latest container images and try again and if it is still broken please LMK!
<!-- gh-comment-id:4188190451 -->
@oschwartz10612 commented on GitHub (Apr 5, 2026):
Hello! I think this was fixed shortly after the release in https://github.com/fosrl/pangolin/issues/2782. Could you pull the latest container images and try again and if it is still broken please LMK!
Hello! I think this was fixed shortly after the release in #2782. Could you pull the latest container images and try again and if it is still broken please LMK!
confirmed it's working now, thanks!
<!-- gh-comment-id:4195068739 -->
@gitmotion commented on GitHub (Apr 6, 2026):
> Hello! I think this was fixed shortly after the release in [#2782](https://github.com/fosrl/pangolin/issues/2782). Could you pull the latest container images and try again and if it is still broken please LMK!
confirmed it's working now, thanks!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @gitmotion on GitHub (Apr 4, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2788
Describe the Bug
After upgrading to
v1.17.0, I was getting ano available servermessage when accessing alocalsite resource.Localsites (newt sites were fine)Workaround:
Not exactly sure what happened, but my guess would be a potential migration issue for local sites??
v1.17.0upgradeJust thought I'd mention this in case and if anyone else ran into the same issue for local sites
Thanks!
Environment
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
@oschwartz10612 commented on GitHub (Apr 5, 2026):
Hello! I think this was fixed shortly after the release in https://github.com/fosrl/pangolin/issues/2782. Could you pull the latest container images and try again and if it is still broken please LMK!
@gitmotion commented on GitHub (Apr 6, 2026):
confirmed it's working now, thanks!