Bug Report: Organization Not Persisting in v1.4.0 #1482

New Issue

MrUnknownDE · 2026-04-05T19:30:26+02:00

MrUnknownDE commented

2026-04-05 19:30:26 +02:00

Originally created by @jakesie1309 on 5/15/2025

After upgrading to Pangolin v1.4.0, the organization setup does not persist correctly across reloads. After a few container restarts or logouts, I'm prompted to re-create the organization. When attempting to do so, I get the error:

Organization ID is already taken. Please choose a different one.
Despite that, I’m unable to proceed or access the existing organization.

Expected Behavior:
The organization and user session should persist across reloads/restarts when data volumes are correctly mounted.

Actual Behavior:

The container starts normally and allows initial organization + Azure AD setup.
After multiple reloads (browser or container restarts), Pangolin "forgets" the session.
Attempting to re-create the organization fails with an “ID already taken” error.
There is no way to log in or reuse the existing org despite correct volume mapping.

Temporary Fix:
I reverted to v1.3.2, and everything works as expected — config persists, and the organization state survives across logouts and reloads.

*Originally created by @jakesie1309 on 5/15/2025* After upgrading to Pangolin v1.4.0, the organization setup does not persist correctly across reloads. After a few container restarts or logouts, I'm prompted to re-create the organization. When attempting to do so, I get the error: Organization ID is already taken. Please choose a different one. Despite that, I’m unable to proceed or access the existing organization. Expected Behavior: The organization and user session should persist across reloads/restarts when data volumes are correctly mounted. Actual Behavior: The container starts normally and allows initial organization + Azure AD setup. After multiple reloads (browser or container restarts), Pangolin "forgets" the session. Attempting to re-create the organization fails with an “ID already taken” error. There is no way to log in or reuse the existing org despite correct volume mapping. Temporary Fix: I reverted to v1.3.2, and everything works as expected — config persists, and the organization state survives across logouts and reloads.

MrUnknownDE closed this issue

2026-04-05 19:30:26 +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#1482