Newt v1.4.0 Binary Shows Token Error on 'newt version' After Manual Update #1152

New Issue

MrUnknownDE · 2026-04-05T18:22:08+02:00

MrUnknownDE commented

2026-04-05 18:22:08 +02:00

Originally created by @jtechbyte on 7/30/2025

First off, I just want to say thank you to the developers for all the great work on Pangolin, I recently migrated all my services from Cloudflare Tunnels to Pangolin, and it’s been a great experience overall. I did run into a small issue after updating the standalone Newt binary (not the Docker version) to v1.4.0. I followed the standard steps to download the binary, make it executable, and move it to /usr/local/bin. While the update itself worked fine running the newt version command correctly shows version 1.4.0 I started getting repeated token errors like Failed to get token with status code: 400. I’ve since removed Newt completely (binary, systemd service, and all related config directories) to start fresh. Also, is this the correct way to perform a manual binary update, or is there a preferred method I might have missed? And finally, is there a proper way to cleanly reset or reconfigure Newt if this happens? Everything else seems to function as expected, but I’d appreciate any guidance and thanks again for building such a solid alternative to Cloudflare Tunnels!

*Originally created by @jtechbyte on 7/30/2025* First off, I just want to say thank you to the developers for all the great work on Pangolin, I recently migrated all my services from Cloudflare Tunnels to Pangolin, and it’s been a great experience overall. I did run into a small issue after updating the standalone Newt binary (not the Docker version) to v1.4.0. I followed the standard steps to download the binary, make it executable, and move it to /usr/local/bin. While the update itself worked fine running the newt version command correctly shows version 1.4.0 I started getting repeated token errors like Failed to get token with status code: 400. I’ve since removed Newt completely (binary, systemd service, and all related config directories) to start fresh. Also, is this the correct way to perform a manual binary update, or is there a preferred method I might have missed? And finally, is there a proper way to cleanly reset or reconfigure Newt if this happens? Everything else seems to function as expected, but I’d appreciate any guidance and thanks again for building such a solid alternative to Cloudflare Tunnels!

MrUnknownDE closed this issue

2026-04-05 18:22:08 +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#1152