Pangolin displays an authorization or permission-related error even when the user is authenticated and logged in with an admin account. The error persists across sessions and occurs while all core Pangolin-related services are running and healthy.
Environment
OS Type & Version: Ubuntu 22.04 LTS
Pangolin Version: fosrl/pangolin:ee-latest
Gerbil Version: fosrl/gerbil:latest
Traefik Version: traefik:v3.4.0
Newt Version: 1.8.1
To Reproduce
Log in to Pangolin using an account with admin privileges.
Access sections or actions that require admin authorization.
Observe that Pangolin reports an authorization/permission error despite the active admin session.
Expected Behavior
Admin users should consistently be recognized as authorized, with full access to admin-only functionality after successful authentication.
Originally created by @blakey108 on GitHub (Jan 7, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2221
### Describe the Bug
Pangolin displays an authorization or permission-related error even when the user is authenticated and logged in with an admin account. The error persists across sessions and occurs while all core Pangolin-related services are running and healthy.
### Environment
OS Type & Version: Ubuntu 22.04 LTS
Pangolin Version: fosrl/pangolin:ee-latest
Gerbil Version: fosrl/gerbil:latest
Traefik Version: traefik:v3.4.0
Newt Version: 1.8.1
### To Reproduce
Log in to Pangolin using an account with admin privileges.
Access sections or actions that require admin authorization.
Observe that Pangolin reports an authorization/permission error despite the active admin session.
### Expected Behavior
Admin users should consistently be recognized as authorized, with full access to admin-only functionality after successful authentication.
@github-actions[bot] commented on GitHub (Jan 22, 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:3781861277 -->
@github-actions[bot] commented on GitHub (Jan 22, 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.
@github-actions[bot] commented on GitHub (Feb 5, 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:3850435301 -->
@github-actions[bot] commented on GitHub (Feb 5, 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.
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 @blakey108 on GitHub (Jan 7, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2221
Describe the Bug
Pangolin displays an authorization or permission-related error even when the user is authenticated and logged in with an admin account. The error persists across sessions and occurs while all core Pangolin-related services are running and healthy.
Environment
OS Type & Version: Ubuntu 22.04 LTS
Pangolin Version: fosrl/pangolin:ee-latest
Gerbil Version: fosrl/gerbil:latest
Traefik Version: traefik:v3.4.0
Newt Version: 1.8.1
To Reproduce
Log in to Pangolin using an account with admin privileges.
Access sections or actions that require admin authorization.
Observe that Pangolin reports an authorization/permission error despite the active admin session.
Expected Behavior
Admin users should consistently be recognized as authorized, with full access to admin-only functionality after successful authentication.
@blakey108 commented on GitHub (Jan 7, 2026):
@github-actions[bot] commented on GitHub (Jan 22, 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.
@github-actions[bot] commented on GitHub (Feb 5, 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.