Originally created by @avczar on GitHub (Nov 4, 2025).
Describe the Bug
Since recent change of the setup script, documentation seems incomplete: the setup sequence is completely changed and user have to guess what to do to get access to /auth/initial-setup, during the 1st phase, but especially at the end.
All containers logs show no errors, but the dashboard seems just inert; so there is nothing that can be done effectively under these conditions.
Environment
OS Type & Version: Debian 13 up to date
Pangolin Version: 1.12.1
Gerbil Version: 1.2.2
Traefik Version: 3.5
Newt Version: N/A
Olm Version: N/A
To Reproduce
Add a fully managed (NS) domain from the cloud dashboard, change DNS server, and waiting the Verified status
Debian & Docker are up to date and ready, without any another custom service installed.
Let all params as default or basic/minimal; w/o SMTP and CrowdSec.
3 containers running / healthy
sudo docker down
Add a node and generate credentials from cloud dashboard
Add given section managed/credentials to the end of ~/config/config.yml via nano and save as sudo
sudo docker up -d
All containers running and logs looks good, without error.
Expected Behavior
Remote node stay offline from the cloud dashboard, even after several minutes.
Not able to access to the pangolin-dashboard.domain.tld / proceed to post-install steps.
Originally created by @avczar on GitHub (Nov 4, 2025).
### Describe the Bug
Since recent change of the setup script, documentation seems incomplete: the setup sequence is completely changed and user have to guess what to do to get access to /auth/initial-setup, during the 1st phase, but especially at the end.
All containers logs show no errors, but the dashboard seems just inert; so there is nothing that can be done effectively under these conditions.
### Environment
- OS Type & Version: Debian 13 up to date
- Pangolin Version: 1.12.1
- Gerbil Version: 1.2.2
- Traefik Version: 3.5
- Newt Version: N/A
- Olm Version: N/A
### To Reproduce
1. Add a fully managed (NS) domain from the cloud dashboard, change DNS server, and waiting the Verified status
2. Debian & Docker are up to date and ready, without any another custom service installed.
3. Just follow your instructions step by step: https://docs.pangolin.net/self-host/quick-install#choose-your-server
4. Let all params as default or basic/minimal; w/o SMTP and CrowdSec.
5. 3 containers running / healthy
6. sudo docker down
7. Add a node and generate credentials from cloud dashboard
8. Add given section managed/credentials to the end of ~/config/config.yml via nano and save as sudo
9. sudo docker up -d
10. All containers running and logs looks good, without error.
### Expected Behavior
Remote node stay offline from the cloud dashboard, even after several minutes.
Not able to access to the pangolin-dashboard.domain.tld / proceed to [post-install steps](https://docs.pangolin.net/self-host/quick-install#post-installation-setup).
Hi, it sounds like you're installing a remote-node that connects to our cloud control plane. If that is the case, the install steps are different from the fully self-hosted docs you linked in. You'd want to check out this instead: https://docs.pangolin.net/manage/remote-node/quick-install-remote
After the remote node comes online, you register it with app.pangolin.net via the ID and secret.
@miloschwartz commented on GitHub (Nov 5, 2025):
Hi, it sounds like you're installing a remote-node that connects to our cloud control plane. If that is the case, the install steps are different from the fully self-hosted docs you linked in. You'd want to check out this instead: https://docs.pangolin.net/manage/remote-node/quick-install-remote
After the remote node comes online, you register it with app.pangolin.net via the ID and secret.
That's it. 😅 I admit it was a bit confusing for me about the hybrid cloud managed mode versus the full self-hosted. Now, I see.
However, URL for the step curl -fsSL https://pangolin.net/get-node-installer.sh | bash not seems works, so you probably need to change by //digpangolin.net/ (working for me): here and here.
@avczar commented on GitHub (Nov 5, 2025):
That's it. 😅 I admit it was a bit confusing for me about the hybrid cloud managed mode versus the full self-hosted. Now, I see.
However, URL for the step `curl -fsSL https://pangolin.net/get-node-installer.sh | bash` not seems works, so you probably need to change by `//digpangolin.net/` (working for me): [here](https://docs.pangolin.net/manage/remote-node/quick-install-remote) and [here](https://docs.pangolin.net/self-host/quick-install).
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 @avczar on GitHub (Nov 4, 2025).
Describe the Bug
Since recent change of the setup script, documentation seems incomplete: the setup sequence is completely changed and user have to guess what to do to get access to /auth/initial-setup, during the 1st phase, but especially at the end.
All containers logs show no errors, but the dashboard seems just inert; so there is nothing that can be done effectively under these conditions.
Environment
To Reproduce
Expected Behavior
Remote node stay offline from the cloud dashboard, even after several minutes.
Not able to access to the pangolin-dashboard.domain.tld / proceed to post-install steps.
@miloschwartz commented on GitHub (Nov 5, 2025):
Hi, it sounds like you're installing a remote-node that connects to our cloud control plane. If that is the case, the install steps are different from the fully self-hosted docs you linked in. You'd want to check out this instead: https://docs.pangolin.net/manage/remote-node/quick-install-remote
After the remote node comes online, you register it with app.pangolin.net via the ID and secret.
@avczar commented on GitHub (Nov 5, 2025):
That's it. 😅 I admit it was a bit confusing for me about the hybrid cloud managed mode versus the full self-hosted. Now, I see.
However, URL for the step
curl -fsSL https://pangolin.net/get-node-installer.sh | bashnot seems works, so you probably need to change by//digpangolin.net/(working for me): here and here.