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

[GH-ISSUE #1827] PIN / Passwort Authentication not working anymore in Pangolin Reverse Proxy 1.12.0 #10778

New Issue
Closed
opened 2026-05-06 15:02:32 -05:00 by GiteaMirror · 14 comments
GiteaMirror commented 2026-05-06 15:02:32 -05:00
Owner
Copy Link

Originally created by @RadioHerzblut on GitHub (Nov 7, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1827

Describe the Bug

Hi everyone,

since updating to Pangolin Reverse Proxy version 1.12.0, the PIN authentication no longer works for any resource. It was working fine before (on 1.11.x).

Has anyone else experienced this issue or knows if something changed in the authentication mechanism?
Could this be a bug in the new release?

Environment

  • OS Type & Version: 24.04 LTS jammy
  • Pangolin Version: 1.12.0
  • Gerbil Version: 1.2.2
  • Traefik Version: 3.5
  • Newt Version: 1.6.0
  • Olm Version: no aktiv

To Reproduce

Hi everyone,

since updating to Pangolin Reverse Proxy version 1.12.0, the PIN authentication no longer works for any resource. It was working fine before (on 1.11.x).

Has anyone else experienced this issue or knows if something changed in the authentication mechanism?
Could this be a bug in the new release?

Originally created by @RadioHerzblut on GitHub (Nov 7, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/1827 ### Describe the Bug Hi everyone, since updating to Pangolin Reverse Proxy version 1.12.0, the PIN authentication no longer works for any resource. It was working fine before (on 1.11.x). Has anyone else experienced this issue or knows if something changed in the authentication mechanism? Could this be a bug in the new release? ### Environment - OS Type & Version: 24.04 LTS jammy - Pangolin Version: 1.12.0 - Gerbil Version: 1.2.2 - Traefik Version: 3.5 - Newt Version: 1.6.0 - Olm Version: no aktiv ### To Reproduce Hi everyone, since updating to Pangolin Reverse Proxy version 1.12.0, the PIN authentication no longer works for any resource. It was working fine before (on 1.11.x). Has anyone else experienced this issue or knows if something changed in the authentication mechanism? Could this be a bug in the new release?
GiteaMirror added the stale label 2026-05-06 15:02:32 -05:00
GiteaMirror commented 2026-05-06 15:02:36 -05:00
Author
Owner
Copy Link

@RadioHerzblut commented on GitHub (Nov 8, 2025):

Info Update:

I have just installed the new Pangolin 1.12.1 update. Unfortunately, the problem with PIN‑ and password‑based authentication persists.

To resolve this, I deleted the affected resources and recreated them. After recreating them, the authentication works correctly again.

BUG ?

<!-- gh-comment-id:3506811879 --> @RadioHerzblut commented on GitHub (Nov 8, 2025): **Info Update**: I have just installed the new Pangolin 1.12.1 update. Unfortunately, the problem with PIN‑ and password‑based authentication persists. To resolve this, I deleted the affected resources and recreated them. After recreating them, the authentication works correctly again. BUG ?
GiteaMirror commented 2026-05-06 15:02:40 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Nov 8, 2025):

What happened when it was not working? Could you walk me through please
what was happening when you were presented with a pin or password and
you entered it and then the failure occurred?

<!-- gh-comment-id:3506829810 --> @oschwartz10612 commented on GitHub (Nov 8, 2025): What happened when it was not working? Could you walk me through please what was happening when you were presented with a pin or password and you entered it and then the failure occurred?
GiteaMirror commented 2026-05-06 15:02:41 -05:00
Author
Owner
Copy Link

@PHLAK commented on GitHub (Nov 9, 2025):

Not sure if this is related but I just updated to v1.12.2 and none of my shared link headers are working.

Never mind, I think this was a configuration issue on my side.

<!-- gh-comment-id:3507503328 --> @PHLAK commented on GitHub (Nov 9, 2025): ~~Not sure if this is related but I just updated to v1.12.2 and none of my shared link headers are working.~~ Never mind, I think this was a configuration issue on my side.
GiteaMirror commented 2026-05-06 15:02:42 -05:00
Author
Owner
Copy Link

@RadioHerzblut commented on GitHub (Nov 9, 2025):

Hello Owen. In my case, I always update to the latest versions. With 1.12.0, I noticed that my services no longer ask for my PIN/password.

I don't have many services, so re-entering the resources is manageable for me.

I'll keep an eye on it!

<!-- gh-comment-id:3508477222 --> @RadioHerzblut commented on GitHub (Nov 9, 2025): Hello Owen. In my case, I always update to the latest versions. With 1.12.0, I noticed that my services no longer ask for my PIN/password. I don't have many services, so re-entering the resources is manageable for me. I'll keep an eye on it!
GiteaMirror commented 2026-05-06 15:02:43 -05:00
Author
Owner
Copy Link

@RadioHerzblut commented on GitHub (Nov 9, 2025):

⚠️Update

Hello,

after today’s update to version 12.1.2, Pangolin started up normally again. The PIN/password prompt also worked — so far, so good.

Then I shut down Docker cleanly, followed by a proper shutdown of the VPS server.

I created a new snapshot and restarted the server.

After the restart, docker ps showed that all services were running correctly, but Pangolin was not reachable.

I then performed a reboot via SSH, and Pangolin became accessible again in the new version.

From that point on, however, the PIN/password prompt no longer worked.

The prompt only appears again after manually restarting the services.

<!-- gh-comment-id:3508606540 --> @RadioHerzblut commented on GitHub (Nov 9, 2025): ⚠️Update Hello, after today’s update to version 12.1.2, Pangolin started up normally again. The PIN/password prompt also worked — so far, so good. Then I shut down Docker cleanly, followed by a proper shutdown of the VPS server. I created a new snapshot and restarted the server. After the restart, docker ps showed that all services were running correctly, but Pangolin was not reachable. I then performed a reboot via SSH, and Pangolin became accessible again in the new version. From that point on, however, the PIN/password prompt no longer worked. The prompt only appears again after manually restarting the services.
GiteaMirror commented 2026-05-06 15:02:45 -05:00
Author
Owner
Copy Link

@plaiddk commented on GitHub (Nov 10, 2025):

Have the same issue. None of my resources prompts for password or login. This is critical. This worked before in v.1.8 - im on v.1.12.1 now.

In v.1.8 i would get the pangolin SSO auth login page before entering my site. Now nothing happens at all. None of the authentication modes get prompted. I have to disable all my sites now.

<!-- gh-comment-id:3514070887 --> @plaiddk commented on GitHub (Nov 10, 2025): Have the same issue. None of my resources prompts for password or login. This is critical. This worked before in v.1.8 - im on v.1.12.1 now. In v.1.8 i would get the pangolin SSO auth login page before entering my site. Now nothing happens at all. None of the authentication modes get prompted. I have to disable all my sites now.
GiteaMirror commented 2026-05-06 15:02:46 -05:00
Author
Owner
Copy Link

@plaiddk commented on GitHub (Nov 11, 2025):

Did you enabled geoblocking? I found out that if i allowed all DK in geoblocking some of my resources ( websites ) would not prompt me with pangolin auth. So i added Pass to Auth instead for my region and denied all others as priority 2. That worked for me

<!-- gh-comment-id:3519054131 --> @plaiddk commented on GitHub (Nov 11, 2025): Did you enabled geoblocking? I found out that if i allowed all DK in geoblocking some of my resources ( websites ) would not prompt me with pangolin auth. So i added Pass to Auth instead for my region and denied all others as priority 2. That worked for me
GiteaMirror commented 2026-05-06 15:02:48 -05:00
Author
Owner
Copy Link

@ptruka commented on GitHub (Nov 24, 2025):

@plaiddk yes, the same happend to me. Maybe a hint "This bypasses authentication" could be shown whenever someone selects "Always Allow" in the Rules.

<!-- gh-comment-id:3572804745 --> @ptruka commented on GitHub (Nov 24, 2025): @plaiddk yes, the same happend to me. Maybe a hint "This bypasses authentication" could be shown whenever someone selects "Always Allow" in the Rules.
GiteaMirror commented 2026-05-06 15:02:50 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 9, 2025):

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:3629635696 --> @github-actions[bot] commented on GitHub (Dec 9, 2025): 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-05-06 15:02:51 -05:00
Author
Owner
Copy Link

@miloschwartz commented on GitHub (Dec 20, 2025):

We renamed these rule types. Hopefully makes it easier to understand.

<!-- gh-comment-id:3677961902 --> @miloschwartz commented on GitHub (Dec 20, 2025): We renamed these rule types. Hopefully makes it easier to understand.
GiteaMirror commented 2026-05-06 15:02:54 -05:00
Author
Owner
Copy Link

@RadioHerzblut commented on GitHub (Dec 20, 2025):

Did you enabled geoblocking? I found out that if i allowed all DK in geoblocking some of my resources ( websites ) would not prompt me with pangolin auth. So i added Pass to Auth instead for my region and denied all others as priority 2. That worked for me

Can you sende Screenshots of the DK Auth. Thanks

<!-- gh-comment-id:3678036072 --> @RadioHerzblut commented on GitHub (Dec 20, 2025): > Did you enabled geoblocking? I found out that if i allowed all DK in geoblocking some of my resources ( websites ) would not prompt me with pangolin auth. So i added Pass to Auth instead for my region and denied all others as priority 2. That worked for me Can you sende Screenshots of the DK Auth. Thanks
GiteaMirror commented 2026-05-06 15:02:59 -05:00
Author
Owner
Copy Link

@RadioHerzblut commented on GitHub (Dec 20, 2025):

Can you sende Screenshots of the DK Auth. Thanks

<!-- gh-comment-id:3678036231 --> @RadioHerzblut commented on GitHub (Dec 20, 2025): Can you sende Screenshots of the DK Auth. Thanks
GiteaMirror commented 2026-05-06 15:03:01 -05:00
Author
Owner
Copy Link

@plaiddk commented on GitHub (Dec 20, 2025):

Can you sende Screenshots of the DK Auth. Thanks

Image
<!-- gh-comment-id:3678038947 --> @plaiddk commented on GitHub (Dec 20, 2025): > Can you sende Screenshots of the DK Auth. Thanks <img width="1498" height="475" alt="Image" src="https://github.com/user-attachments/assets/b8e4a964-26a8-4f0e-a815-23b33a95d79e" />
GiteaMirror commented 2026-05-06 15:03:02 -05:00
Author
Owner
Copy Link

@RadioHerzblut commented on GitHub (Dec 20, 2025):

Thanks plaiddk. So it works for me Pangolin too. 👍

<!-- gh-comment-id:3678168291 --> @RadioHerzblut commented on GitHub (Dec 20, 2025): Thanks plaiddk. So it works for me Pangolin too. 👍
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#10778
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?