mirror of
https://github.com/fosrl/pangolin.git
synced 2026-05-06 20:59:07 -05:00
[GH-ISSUE #1171] Newt v1.4.0 Binary Shows Token Error on 'newt version' After Manual Update #1792
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/pangolin#1792
Reference in New Issue
Block a user
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?
Originally created by @jtechbyte on GitHub (Jul 30, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1171
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!
@oschwartz10612 commented on GitHub (Jul 30, 2025):
Are you on a ipv6 network? looking into a fix now but heard that on Discord.
@jtechbyte commented on GitHub (Jul 30, 2025):
Thanks for the quick reply! I just checked, and my server doesn’t appear to be on an IPv6 network. It only has link-local fe80:: addresses, and ping6 google.com returns “Network is unreachable,” so there’s no global IPv6 connectivity. Appreciate you looking into it!
@oschwartz10612 commented on GitHub (Jul 30, 2025):
Oh! Are you running with the cli args (--id, --secret, etc...) or are you just running newt and relying on it pulling out of the file. I think I changed the file location so that could be it.
@jtechbyte commented on GitHub (Jul 30, 2025):
I followed the install steps from the official Newt docs downloaded the latest binary, made it executable, moved it to /usr/local/bin (replacing the existing newt binary), and updated my newt.service file to include my saved --id, --secret, and --endpoint values.
@oschwartz10612 commented on GitHub (Jul 30, 2025):
New question sorry haha. Any logs from pangolin that could help?
docker compose logs -f pangolin? Also anything from running newt with --log-level debug?@jtechbyte commented on GitHub (Jul 30, 2025):
Sure, here are my Docker logs from my VPS, along with the Newt logs from my home server. Just a heads up you might not see any errors, since I did a clean install of Newt earlier before posting this issue. Also, for privacy reasons, I’ve redacted my private IP address and domain name in the logs.
Docker Logs.txt
Newt Logs.txt
@oschwartz10612 commented on GitHub (Jul 31, 2025):
Yeah from the logs it looks like it works? Also from the same report on discord it seems like it works? I am going to close but please reopen if it comes back!
@jtechbyte commented on GitHub (Jul 31, 2025):
Thank you, for your time, will do!