[GH-ISSUE #1093] First time install, failing to connect/set up site via Newt, getting token failure, HTTP 400. #1760

Closed
opened 2026-04-16 08:34:17 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @IJOY94 on GitHub (Jul 19, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1093

I followed the setup through the VPS cli configuration, but I'm getting the following error when I try to set up a site:

ERROR: 2025/07/19 02:58:22 Failed to get token with status code: 400
ERROR: 2025/07/19 02:58:22 Failed to connect: failed to get token: failed to get token with status code: 400. Retrying in 3s...

As far as I can see, my Debian 12 VPS should have the firewall set up correctly:

$ sudo ufw status
Status: active

To                         Action      From
--                         ------      ----
80/tcp                     ALLOW       Anywhere                  
443/tcp                    ALLOW       Anywhere                  
44/tcp                     ALLOW       Anywhere                  
51820/udp                  ALLOW       Anywhere                  
80/tcp (v6)                ALLOW       Anywhere (v6)             
443/tcp (v6)               ALLOW       Anywhere (v6)             
44/tcp (v6)                ALLOW       Anywhere (v6)             
51820/udp (v6)             ALLOW       Anywhere (v6)

and I can get to the pangolin webconfig just fine, but the Newt tunnel won't establish itself. This is likely a configuration error, but I don't know how to go from "Bad Request" to what's actually wrong here.

Originally created by @IJOY94 on GitHub (Jul 19, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/1093 I followed the setup through the VPS cli configuration, but I'm getting the following error when I try to set up a site: ``` ERROR: 2025/07/19 02:58:22 Failed to get token with status code: 400 ERROR: 2025/07/19 02:58:22 Failed to connect: failed to get token: failed to get token with status code: 400. Retrying in 3s... ``` As far as I can see, my Debian 12 VPS should have the firewall set up correctly: ``` $ sudo ufw status Status: active To Action From -- ------ ---- 80/tcp ALLOW Anywhere 443/tcp ALLOW Anywhere 44/tcp ALLOW Anywhere 51820/udp ALLOW Anywhere 80/tcp (v6) ALLOW Anywhere (v6) 443/tcp (v6) ALLOW Anywhere (v6) 44/tcp (v6) ALLOW Anywhere (v6) 51820/udp (v6) ALLOW Anywhere (v6) ``` and I can get to the pangolin webconfig just fine, but the Newt tunnel won't establish itself. This is likely a configuration error, but I don't know how to go from "Bad Request" to what's actually wrong here.
Author
Owner

@IJOY94 commented on GitHub (Jul 19, 2025):

Solved: I had not yet created the site. I guess I expected the token server to be live as soon as I was presented with the credentials.

Below is what made it "click":
https://youtu.be/8VdwOL7nYkY?t=1126

<!-- gh-comment-id:3091991875 --> @IJOY94 commented on GitHub (Jul 19, 2025): Solved: I had not yet created the site. I guess I expected the token server to be live as soon as I was presented with the credentials. Below is what made it "click": https://youtu.be/8VdwOL7nYkY?t=1126
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#1760