github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-21 09:21:15 -05:00
Code Issues 856 Packages Projects Releases 74 Wiki Activity

Installer doesn't produce initial install administrator's code to create admin account #762

New Issue
Closed
opened 2025-11-13 12:10:16 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-13 12:10:16 -06:00
Owner
Copy Link

Originally created by @devinhedge on GitHub (Nov 5, 2025).

Describe the Bug

I don't know what to say other than what the title says.

I used the installer, had to wipe the machine, re-ran the installer, destroyed the machine and created a new VPS for a clean install. Each time the installer never produced the first login admin key so I could never finish setting up the pangolin server.

I look at how well this is using multiple FOSS tools integrated together and can appreciate the difficulty in getting the "first run" install to just work and I'm amazed that it even goes as far as it does. Well done. Without the ability to "regenerate" or get that admin key, it's useless to me.

Environment

  • OS Type & Version: 24.04LTS
  • Pangolin Version: latest in release installer as of 04-NOV-2025
  • Gerbil Version: latest in release installer as of 04-NOV-2025
  • Traefik Version:latest in release installer as of 04-NOV-2025
  • Newt Version:latest in release installer as of 04-NOV-2025
  • Olm Version: ???

To Reproduce

Steps to recreate:

  1. curl -fsSL https://pangolin.net/get-installer.sh | bash
  2. sudo ./installer
  3. Configure basic settings
  4. Say no to email support
  5. Installation begins
  6. Install CrowdSec
  7. The final installation notice listed on the quick install guide never happens. This:
Installation complete!

To complete the initial setup, please visit:
https://pangolin.example.com/auth/initial-setup

  1. Access the dashboard and everything looks fine

  2. I don't have the Setup Token to continue.

Image

Expected Behavior

Setup token generated during installation so I can complete the server configuration through the web page.

Originally created by @devinhedge on GitHub (Nov 5, 2025). ### Describe the Bug I don't know what to say other than what the title says. I used the installer, had to wipe the machine, re-ran the installer, destroyed the machine and created a new VPS for a clean install. Each time the installer never produced the first login admin key so I could never finish setting up the pangolin server. I look at how well this is using multiple FOSS tools integrated together and can appreciate the difficulty in getting the "first run" install to **just work** and I'm amazed that it even goes as far as it does. Well done. Without the ability to "regenerate" or get that admin key, it's useless to me. ### Environment - OS Type & Version: 24.04LTS - Pangolin Version: latest in release installer as of 04-NOV-2025 - Gerbil Version: latest in release installer as of 04-NOV-2025 - Traefik Version:latest in release installer as of 04-NOV-2025 - Newt Version:latest in release installer as of 04-NOV-2025 - Olm Version: ??? ### To Reproduce Steps to recreate: 1. ```curl -fsSL https://pangolin.net/get-installer.sh | bash``` 2. ```sudo ./installer``` 3. Configure basic settings 4. Say no to email support 5. Installation begins 6. Install CrowdSec 7. The final installation notice listed on the quick install guide never happens. This: ```bash Installation complete! To complete the initial setup, please visit: https://pangolin.example.com/auth/initial-setup ``` 8. Access the dashboard and everything looks fine 9. I don't have the Setup Token to continue. <img width="936" height="1352" alt="Image" src="https://github.com/user-attachments/assets/4590cae2-01fe-4486-aa06-790bb9672a0b" /> ### Expected Behavior Setup token generated during installation so I can complete the server configuration through the web page.
GiteaMirror commented 2025-11-13 12:10:17 -06:00
Author
Owner
Copy Link

@miloschwartz commented on GitHub (Nov 5, 2025):

If you run docker compose down then docker compose up and watch the logs on startup, it should print the token somewhere in the logs statements.

@miloschwartz commented on GitHub (Nov 5, 2025): If you run `docker compose down` then `docker compose up` and watch the logs on startup, it should print the token somewhere in the logs statements.
GiteaMirror commented 2025-11-13 12:10:17 -06:00
Author
Owner
Copy Link

@devinhedge commented on GitHub (Nov 5, 2025):

I appreciate the work-around. I'll give that a try.

Even so, either the docs need to be updated (documentation bug), or the code needs to be fixed (code bug).

I ran into a different behavior while trying to install that I commented on here. I now have a feeling that it may be related some how. Even though the previous error was likely a transient problem with downloading the docker images, I think there is some bit of the installer code that isn't handling bringing up the docker instances in a way that handles all of the permutations that isn't being caught and so it appears the installer is ending prematurely before passing back the admin code and completion message.

@devinhedge commented on GitHub (Nov 5, 2025): I appreciate the work-around. I'll give that a try. Even so, either the docs need to be updated (documentation bug), or the code needs to be fixed (code bug). I ran into a different behavior while trying to install that I commented on [here](https://github.com/fosrl/pangolin/issues/1068). I now have a feeling that it may be related some how. Even though the previous error was likely a transient problem with downloading the docker images, I think there is some bit of the installer code that isn't handling bringing up the docker instances in a way that handles all of the permutations that isn't being caught and so it appears the installer is ending prematurely before passing back the admin code and completion message.
GiteaMirror commented 2025-11-13 12:10:17 -06:00
Author
Owner
Copy Link

@devinhedge commented on GitHub (Nov 5, 2025):

I was able to get the admin key using tmux split screen, split the window, ran sudo docker logs -f pangolin in one window, and docker compose down then docker compose up in the other.

I definately think there is something going on in the installer, though.

What a wonderful thing that has been created here. Many thanks to the developers.

@devinhedge commented on GitHub (Nov 5, 2025): I was able to get the admin key using `tmux` split screen, split the window, ran `sudo docker logs -f pangolin` in one window, and `docker compose down` then `docker compose up` in the other. I definately think there is something going on in the installer, though. What a wonderful thing that has been created here. Many thanks to the developers.
GiteaMirror commented 2025-11-13 12:10:17 -06:00
Author
Owner
Copy Link

@miloschwartz commented on GitHub (Nov 5, 2025):

Thanks @devinhedge glad you got it working. Will try to replicate the install, but closing this for now.

@miloschwartz commented on GitHub (Nov 5, 2025): Thanks @devinhedge glad you got it working. Will try to replicate the install, but closing this for now.
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
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#762
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?