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 GitHub (May 15, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/734
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.
I upgraded Pangolin from v1.3.2 to v1.4.0, and everything seems to be working as expected this time.
The organization details were retained.
I have automation provisioning turned off on my identity provider.
No issues so far with the config or startup.
I'll continue to monitor and update if anything breaks, but so far looks good!
<!-- gh-comment-id:2888103643 -->
@jakesie1309 commented on GitHub (May 17, 2025):
just a quick update.
I upgraded Pangolin from v1.3.2 to v1.4.0, and everything seems to be working as expected this time.
The organization details were retained.
I have automation provisioning turned off on my identity provider.
No issues so far with the config or startup.
I'll continue to monitor and update if anything breaks, but so far looks good!
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 @jakesie1309 on GitHub (May 15, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/734
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.
@jakesie1309 commented on GitHub (May 17, 2025):
just a quick update.
I upgraded Pangolin from v1.3.2 to v1.4.0, and everything seems to be working as expected this time.
The organization details were retained.
I have automation provisioning turned off on my identity provider.
No issues so far with the config or startup.
I'll continue to monitor and update if anything breaks, but so far looks good!