First time install, failing to connect/set up site via Newt, getting token failure, HTTP 400. #1211

New Issue

MrUnknownDE · 2026-04-05T18:31:49+02:00

MrUnknownDE commented

2026-04-05 18:31:49 +02:00

Originally created by @IJOY94 on 7/19/2025

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 7/19/2025* 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.

MrUnknownDE closed this issue

2026-04-05 18:31:49 +02:00

Sign in to join this conversation.

Branches Tags

main

dev

dependabot/npm_and_yarn/dev-minor-updates-b4e5d6b9c5

revert-2766-feature/systemd-install-instructions

dependabot/npm_and_yarn/prod-patch-updates-05702d39f2

dependabot/npm_and_yarn/next-16.2.1

dependabot/npm_and_yarn/recharts-3.8.1

alerting-rules

private-site-ha

dependabot/docker/docker/library/node-25-slim

ssh

delete-account

msg-delivery

org-only-idp

cicd

patch

site-targets-auto-login

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/pangolin#1211