github-starred/newt
2
0
Fork 0
mirror of https://github.com/fosrl/newt.git synced 2026-03-09 07:12:28 -05:00
Code Issues 21 Packages Projects Releases 25 Wiki Activity

Newt failed to connect on fresh install #9

New Issue
Closed
opened 2025-11-19 07:11:39 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-19 07:11:39 -06:00
Owner
Copy Link

Originally created by @Lokowitz on GitHub (Mar 1, 2025).

Hey guys,

yesterday i tried the new pangolin update and i made a fresh install on the vps.
Now i can not connect the newt site with docker, i tried docker compose and the docker run command.
It is only working with the binary newt installation.

All running on latest tag and i also tried with secound LXC container.

ERROR: 2025/03/01 08:27:16 Failed to connect: failed to get token: failed to decode token response: EOF. Retrying in 10s...
ERROR: 2025/03/01 08:27:27 Failed to connect: failed to get token: failed to decode token response: EOF. Retrying in 10s...
ERROR: 2025/03/01 08:27:37 Failed to connect: failed to get token: failed to decode token response: EOF. Retrying in 10s...
^X^Cpanic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x7cddb8]

goroutine 1 [running]:
golang.zx2c4.com/wireguard/device.(*Device).Close(0x0)
        /go/pkg/mod/golang.zx2c4.com/wireguard@v0.0.0-20231211153847-12269c276173/device/device.go:371 +0x38
main.main()
        /app/main.go:552 +0xe66
Originally created by @Lokowitz on GitHub (Mar 1, 2025). Hey guys, yesterday i tried the new pangolin update and i made a fresh install on the vps. Now i can not connect the newt site with docker, i tried docker compose and the docker run command. It is only working with the binary newt installation. All running on latest tag and i also tried with secound LXC container. ``` ERROR: 2025/03/01 08:27:16 Failed to connect: failed to get token: failed to decode token response: EOF. Retrying in 10s... ERROR: 2025/03/01 08:27:27 Failed to connect: failed to get token: failed to decode token response: EOF. Retrying in 10s... ERROR: 2025/03/01 08:27:37 Failed to connect: failed to get token: failed to decode token response: EOF. Retrying in 10s... ^X^Cpanic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x7cddb8] goroutine 1 [running]: golang.zx2c4.com/wireguard/device.(*Device).Close(0x0) /go/pkg/mod/golang.zx2c4.com/wireguard@v0.0.0-20231211153847-12269c276173/device/device.go:371 +0x38 main.main() /app/main.go:552 +0xe66 ```
GiteaMirror commented 2025-11-19 07:11:41 -06:00
Author
Owner
Copy Link

@Mitch187 commented on GitHub (Mar 2, 2025):

I have the same problem, too.

@Mitch187 commented on GitHub (Mar 2, 2025): I have the same problem, too.
GiteaMirror commented 2025-11-19 07:11:41 -06:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Mar 2, 2025):

Typically this is due to something wrong with getting the token from the server - usually a wrong endpoint or bad credentials. Does the endpoint in your newt command match the dashboard? Does it have any extra chars?

In 3d15ecb I am printing the actual response which may help us narrow down this issue. I should be rolling this out shortly.

@oschwartz10612 commented on GitHub (Mar 2, 2025): Typically this is due to something wrong with getting the token from the server - usually a wrong endpoint or bad credentials. Does the endpoint in your newt command match the dashboard? Does it have any extra chars? In [3d15ecb](https://github.com/fosrl/newt/commit/3d15ecb7327e97a49c9b7e26b5b421a2b5bb7d6f) I am printing the actual response which may help us narrow down this issue. I should be rolling this out shortly.
GiteaMirror commented 2025-11-19 07:11:41 -06:00
Author
Owner
Copy Link

@Lokowitz commented on GitHub (Mar 3, 2025):

It is working for me now...
I deleted the pangolin installation on the vps and reinstalled it, but this time without crowdsec installation at the first time.
After finishing my setup (dnschallenge, 2 sites added, 9 resources added) i added crowdsec via the installer and everything is still working fine now.
The only thing i noticed from my old installation is that in the dynamic_config.yml i still had "crowdsecLapiKey: "PUT_YOUR_BOUNCER_KEY_HERE_OR_IT_WILL_NOT_WORK"", so it sounds like the installation was not complete. In my current installation the bouncer key is inserted.

@Mitch187 did you also installed crowdsec with initial installation? And is your bouncer key replaced in dynamic_config.yml?

@Lokowitz commented on GitHub (Mar 3, 2025): It is working for me now... I deleted the pangolin installation on the vps and reinstalled it, but this time without crowdsec installation at the first time. After finishing my setup (dnschallenge, 2 sites added, 9 resources added) i added crowdsec via the installer and everything is still working fine now. The only thing i noticed from my old installation is that in the dynamic_config.yml i still had "crowdsecLapiKey: "PUT_YOUR_BOUNCER_KEY_HERE_OR_IT_WILL_NOT_WORK"", so it sounds like the installation was not complete. In my current installation the bouncer key is inserted. @Mitch187 did you also installed crowdsec with initial installation? And is your bouncer key replaced in dynamic_config.yml?
GiteaMirror commented 2025-11-19 07:11:41 -06:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Mar 3, 2025):

Ahh yeah this makes sense. Pesky crowdsec. It must have been blocking you. Looks like it failed when you installed the first time to automate the token retrial. I will see if I can update the script to more explicitly fail if that is the case.

@oschwartz10612 commented on GitHub (Mar 3, 2025): Ahh yeah this makes sense. Pesky crowdsec. It must have been blocking you. Looks like it failed when you installed the first time to automate the token retrial. I will see if I can update the script to more explicitly fail if that is the case.
GiteaMirror commented 2025-11-19 07:11:41 -06:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Mar 3, 2025):

Added a check in 37fdc4a6a8 to warn users

@oschwartz10612 commented on GitHub (Mar 3, 2025): Added a check in https://github.com/fosrl/pangolin/commit/37fdc4a6a85a9f4af548bed4461b8ea575dcba9d to warn users
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
good first issue
help wanted
Improvement
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/newt#9
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?