github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-06 12:55:03 -05:00
Code Issues 564 Packages Projects Releases 72 Wiki Activity

[GH-ISSUE #2263] Apache Guacamole errors after upgrading Pangolin from 1.13.1 to 1.14.1, Newt from 1.7.0 to 1.8.1 and Traefik from 3.6.5 to 3.6.6. #8885

New Issue
Closed
opened 2026-04-30 04:59:28 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-30 04:59:28 -05:00
Owner
Copy Link

Originally created by @DaveCorsello on GitHub (Jan 18, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2263

After upgrading Pangolin from 1.13.1 to 1.14.1, Newt from 1.7.0 to 1.8.1 and Traefik from 3.6.5 to 3.6.6., logging into Apache Guacamole, a public resource in Pangolin, became unreliable. After entering MFA in Guacamole, its UI showed the generic message:

“An error has occurred and this action cannot be completed…”

Key observations:

Traefik access logs showed POST /guacamole/api/tokens alternating between:

  • 502 (upstream unreachable / bad gateway),

  • 500 with no ServiceName (request handled before routing; suggests router/service missing temporarily / dynamic config instability),

  • and occasionally 403 from the backend (Guacamole returned JSON 403).

Pangolin-generated Traefik config routed Guacamole to a dynamic overlay endpoint:

I have searched for other recent discussions in this forum on the topic of api tokens and have found none.

Gerbil's WireGuard interface:

  • wg0 on 100.89.128.1/24,

Newt 1.8.1 logs on the remote side repeatedly showed:

  • Ping failed ... recurring every minute (this happens across multiple versions of Newt and doesn't seem to me to be related to the Guacamole problems)

  • Connection to server lost ... reconnecting,

  • then Tunnel connection established ... Started tcp proxy to <guacamole's private IP>:8080

This reconnection loop correlated with the 502/500 bursts and errors/inaccessible pages in the Guacamole UI.

Rollback and roll forward results:

Rolling back Pangolin to 1.13.1, Newt to 1.7.0 and Traefik to 3.6.5 restored Guacamole stability.
Rolling forward Pangolin to 1.14.1 and Newt to 1.8.1 while keeping Traefik fixed at 3.6.5 resulted in the Guacamole issues described above.
Rolling back Pangolin and Newt to version 1.13.1 and 1.7.0 respectively again restored Guacamole stability.

Conclusion:

It appears that the errors in Guacamole were caused by upgrading to Pangolin 1.14.1 and Newt 1.8.1.

Originally posted by @DaveCorsello in https://github.com/fosrl/pangolin/discussions/2234

Originally created by @DaveCorsello on GitHub (Jan 18, 2026). Original GitHub issue: https://github.com/fosrl/pangolin/issues/2263 After upgrading Pangolin from 1.13.1 to 1.14.1, Newt from 1.7.0 to 1.8.1 and Traefik from 3.6.5 to 3.6.6., logging into Apache Guacamole, a public resource in Pangolin, became unreliable. After entering MFA in Guacamole, its UI showed the generic message: “An error has occurred and this action cannot be completed…” **Key observations:** Traefik access logs showed POST /guacamole/api/tokens alternating between: - 502 (upstream unreachable / bad gateway), - 500 with no ServiceName (request handled before routing; suggests router/service missing temporarily / dynamic config instability), - and occasionally 403 from the backend (Guacamole returned JSON 403). Pangolin-generated Traefik config routed Guacamole to a dynamic overlay endpoint: - 1-Guacamole-service -> http://100.89.128.16:<ephemeral_port> I have searched for other recent discussions in this forum on the topic of api tokens and have found none. Gerbil's WireGuard interface: - wg0 on 100.89.128.1/24, Newt 1.8.1 logs on the remote side repeatedly showed: - Ping failed ... recurring every minute (this happens across multiple versions of Newt and doesn't seem to me to be related to the Guacamole problems) - Connection to server lost ... reconnecting, - then Tunnel connection established ... Started tcp proxy to <guacamole's private IP>:8080 This reconnection loop correlated with the 502/500 bursts and errors/inaccessible pages in the Guacamole UI. **Rollback and roll forward results:** Rolling back Pangolin to 1.13.1, Newt to 1.7.0 and Traefik to 3.6.5 restored Guacamole stability. Rolling forward Pangolin to 1.14.1 and Newt to 1.8.1 while keeping Traefik fixed at 3.6.5 resulted in the Guacamole issues described above. Rolling back Pangolin and Newt to version 1.13.1 and 1.7.0 respectively again restored Guacamole stability. **Conclusion:** It appears that the errors in Guacamole were caused by upgrading to Pangolin 1.14.1 and Newt 1.8.1. _Originally posted by @DaveCorsello in https://github.com/fosrl/pangolin/discussions/2234_
GiteaMirror added the stale label 2026-04-30 04:59:28 -05:00
GiteaMirror commented 2026-04-30 04:59:32 -05:00
Author
Owner
Copy Link

@DaveCorsello commented on GitHub (Jan 27, 2026):

In test instances of Pangolin/Newt and Guacamole, after upgrading to Pangolin 1.15.1 and Newt to 1.9.0, the error in Guacamole has not appeared.

<!-- gh-comment-id:3808109887 --> @DaveCorsello commented on GitHub (Jan 27, 2026): In test instances of Pangolin/Newt and Guacamole, after upgrading to Pangolin 1.15.1 and Newt to 1.9.0, the error in Guacamole has not appeared.
GiteaMirror commented 2026-04-30 04:59:34 -05:00
Author
Owner
Copy Link

@ghosthvj commented on GitHub (Jan 29, 2026):

Hi, I've updated to Pangolin 1.15.1 and Newt 1.9.0, and Apache Guacamole isn't working behind Pangolin.

It doesn't even display the authentication form
keeps showing this error:

Image
<!-- gh-comment-id:3820861980 --> @ghosthvj commented on GitHub (Jan 29, 2026): Hi, I've updated to Pangolin 1.15.1 and Newt 1.9.0, and Apache Guacamole isn't working behind Pangolin. It doesn't even display the authentication form keeps showing this error: <img width="964" height="391" alt="Image" src="https://github.com/user-attachments/assets/57aff4e7-dc59-480c-a537-934dea05ece3" />
GiteaMirror commented 2026-04-30 04:59:35 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 13, 2026):

This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.

<!-- gh-comment-id:3894168083 --> @github-actions[bot] commented on GitHub (Feb 13, 2026): This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
GiteaMirror commented 2026-04-30 04:59:35 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 28, 2026):

This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.

<!-- gh-comment-id:3975861606 --> @github-actions[bot] commented on GitHub (Feb 28, 2026): This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label stale
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#8885
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?