mirror of
https://github.com/fosrl/pangolin.git
synced 2026-05-21 17:20:36 -05:00
Newt on client: too many colons in address #681
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 @Viceman256 on GitHub (Sep 22, 2025).
Ran fine yesterday. Tried running the command today for my client and it fails to process:
INFO: 2025/09/21 21:43:40 Newt version 1.5.0
INFO: 2025/09/21 21:43:43 Websocket connected
ERROR: 2025/09/21 21:43:43 Failed to split endpoint: address https://[url]:51820: too many colons in address
The domain is entered exactly how it was provided from the portal, as well as the same way it's entered on my other clients. This client specifically is a raspberry pi.
@oschwartz10612 commented on GitHub (Sep 22, 2025):
Are you on ipv6 by chance? This could be related to invalid parsing of
ipv6 addresses. I think there is an open pr to fix this - need to look
into merging.
@Viceman256 commented on GitHub (Sep 22, 2025):
Thanks for the super quick response! Both devices do have IPv6 enabled, but I'm unsure how to determine if it's routing through Ipv6. When I ping my server from my pi, it shows an ipv4 address, so I believe it should be routing through ipv4. In gerbil logs, I'm also seeing ipv4 addresses:
INFO: 2025/09/22 02:48:09 Peer [peer] added successfully
INFO: 2025/09/22 02:53:46 Clearing connections for removed peer with WG IP: [ip]
INFO: 2025/09/22 02:53:46 Cleared 0 connections for WG IP: [ip]
INFO: 2025/09/22 02:53:46 Peer [peer] removed successfully
INFO: 2025/09/22 02:53:46 Clearing connections for added peer with WG IP: [ip]
INFO: 2025/09/22 02:53:46 Cleared 0 connections for WG IP: [ip]
INFO: 2025/09/22 02:53:46 Peer [peer] added successfully
ETA:
I just removed IPv6 from my VPS and it still seems to present the same issue. Thanks for the idea though!
I also created a new site just to test that, presented the same issue on the client. I also uninstalled newt on the client and just reinstalled, same behavior.
@Viceman256 commented on GitHub (Sep 22, 2025):
Lastly, when I signed in my other clients were working well. I rebooted my VPS during testing when I disabled ipv6, and now all clients are giving me this colon error. Even those I haven't touched since yesterday.
Tested disabling firewall on VPS (Hetzner) and no luck. They can ping the server fine. Docker logs show pangolin is creating a websocket connection successfully too. Newt just for some reason seems to be putting a colon at the end of the addresses.
@AstralDestiny commented on GitHub (Sep 23, 2025):
https://github.com/fosrl/olm/issues/8 This one @oschwartz10612 ?
@oschwartz10612 commented on GitHub (Sep 23, 2025):
Yeah @AstralDestiny thats what I am thinking not sure need to spend some
time on this lol.