[GH-ISSUE #1509] Setup token not displayed after installation #10694

Closed
opened 2026-05-06 14:32:08 -05:00 by GiteaMirror · 9 comments
Owner

Originally created by @Datzmexxx on GitHub (Sep 20, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1509

Originally assigned to: @oschwartz10612 on GitHub.

I installed pangolin using the installer as on the quick install guide and after the installation was completed the setup token was not displayed. However, the initial setup page on my domain still asks for the setup token. I suppose this is a bug.

Originally created by @Datzmexxx on GitHub (Sep 20, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/1509 Originally assigned to: @oschwartz10612 on GitHub. I installed pangolin using the installer as on the quick install guide and after the installation was completed the setup token was not displayed. However, the initial setup page on my domain still asks for the setup token. I suppose this is a bug.
GiteaMirror added the non-critical bugbug labels 2026-05-06 14:32:09 -05:00
Author
Owner

@DanielPantle commented on GitHub (Sep 21, 2025):

I got the same problem. As a workaround you can run docker logs pangolin, in the output I found this section:

=== SETUP TOKEN EXISTS ===
Token: xxx
Use this token on the initial setup page
================================

With this token, I was able to create the admin account.

<!-- gh-comment-id:3315914265 --> @DanielPantle commented on GitHub (Sep 21, 2025): I got the same problem. As a workaround you can run `docker logs pangolin`, in the output I found this section: ``` === SETUP TOKEN EXISTS === Token: xxx Use this token on the initial setup page ================================ ``` With this token, I was able to create the admin account.
Author
Owner

@Datzmexxx commented on GitHub (Sep 21, 2025):

I got the same problem. As a workaround you can run docker logs pangolin, in the output I found this section:

=== SETUP TOKEN EXISTS ===
Token: xxx
Use this token on the initial setup page
================================

With this token, I was able to create the admin account.

Thanks. This sorted it out

<!-- gh-comment-id:3316161171 --> @Datzmexxx commented on GitHub (Sep 21, 2025): > I got the same problem. As a workaround you can run `docker logs pangolin`, in the output I found this section: > > ``` > === SETUP TOKEN EXISTS === > Token: xxx > Use this token on the initial setup page > ================================ > ``` > > With this token, I was able to create the admin account. Thanks. This sorted it out
Author
Owner

@oschwartz10612 commented on GitHub (Sep 22, 2025):

I think the installer was updated to fix this. Please reopen if not.

<!-- gh-comment-id:3316395080 --> @oschwartz10612 commented on GitHub (Sep 22, 2025): I think the installer was updated to fix this. Please reopen if not.
Author
Owner

@aries223 commented on GitHub (Oct 14, 2025):

This is still happening when selecting the CrowdSec option. If you do not select CrowdSec, it works fine.

<!-- gh-comment-id:3403244648 --> @aries223 commented on GitHub (Oct 14, 2025): This is still happening when selecting the CrowdSec option. If you do not select CrowdSec, it works fine.
Author
Owner

@federicoiosue commented on GitHub (Oct 24, 2025):

This is still happening when selecting the CrowdSec option. If you do not select CrowdSec, it works fine.

Same here

<!-- gh-comment-id:3445214180 --> @federicoiosue commented on GitHub (Oct 24, 2025): > This is still happening when selecting the CrowdSec option. If you do not select CrowdSec, it works fine. Same here
Author
Owner

@Jeff4Success commented on GitHub (Oct 27, 2025):

Just installed, manual self-host, and as mentioned, I picked CrowdSec and wasn't shown the token. But looking at the logs still works.

<!-- gh-comment-id:3452949357 --> @Jeff4Success commented on GitHub (Oct 27, 2025): Just installed, manual self-host, and as mentioned, I picked CrowdSec and wasn't shown the token. But looking at the logs still works.
Author
Owner

@ghost commented on GitHub (Nov 12, 2025):

Still an issue, logs workaround does show the token.

<!-- gh-comment-id:3521994967 --> @ghost commented on GitHub (Nov 12, 2025): Still an issue, logs workaround does show the token.
Author
Owner

@gallagherman commented on GitHub (Nov 20, 2025):

Just installed today from the pre-configured digitalocean droplet and this occurred. I did install crowdsec. I found it in the docker logs.

<!-- gh-comment-id:3559788878 --> @gallagherman commented on GitHub (Nov 20, 2025): Just installed today from the pre-configured digitalocean droplet and this occurred. I did install crowdsec. I found it in the docker logs.
Author
Owner

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

Tracking in #1903

<!-- gh-comment-id:3566901508 --> @oschwartz10612 commented on GitHub (Nov 22, 2025): Tracking in #1903
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#10694