[GH-ISSUE #911] [Bug] Newt agent registration fails with "HTTP error! status: undefined" #1688

Closed
opened 2026-04-16 08:25:51 -05:00 by GiteaMirror · 3 comments
Owner

Originally created by @lionfish2 on GitHub (Jun 14, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/911

After successfully installing and connecting a fosrl/newt agent to a Pangolin v1.5.1 instance, the agent remains "Offline" in the UI. The Pangolin logs show an HTTP error! status: undefined immediately after handling the agent's registration message.

Versions:
Pangolin: fosrl/pangolin:1.5.1
Newt Agent: fosrl/newt:latest
CrowdSec: crowdsecurity/crowdsec:latest (v1.6.8)
Traefik: v3.4.1

Pangolin Log Error:
INFO: WebSocket connection established - Newt ID: [REDACTED]
INFO: Handling register message!
INFO: Public key mismatch. Deleting old peer...
ERROR: Message handling error: HTTP error! status: undefined
Stack: Error: HTTP error! status: undefined
at bo (file:///app/dist/server.mjs:25:32177)

Troubleshooting Steps Performed:
I have confirmed that the issue is not with the CrowdSec LAPI itself.

  1. Networking between the pangolin and crowdsec containers is working.
  2. A curl -v http://crowdsec:8080/v1/health from inside the pangolin container results in a 404 Not Found.
  3. However, the CrowdSec LAPI is functional. The Traefik bouncer connects successfully, and a manually registered test-bouncer using cscli bouncers add also validates successfully, showing a ✔️ in cscli bouncers list.

This proves the LAPI is working for standard bouncers, but the Pangolin application fails when it tries to communicate with it during Newt registration.

Originally created by @lionfish2 on GitHub (Jun 14, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/911 After successfully installing and connecting a fosrl/newt agent to a Pangolin v1.5.1 instance, the agent remains "Offline" in the UI. The Pangolin logs show an HTTP error! status: undefined immediately after handling the agent's registration message. **Versions:** Pangolin: fosrl/pangolin:1.5.1 Newt Agent: fosrl/newt:latest CrowdSec: crowdsecurity/crowdsec:latest (v1.6.8) Traefik: v3.4.1 **Pangolin Log Error:** INFO: WebSocket connection established - Newt ID: [REDACTED] INFO: Handling register message! INFO: Public key mismatch. Deleting old peer... ERROR: Message handling error: HTTP error! status: undefined Stack: Error: HTTP error! status: undefined at bo (file:///app/dist/server.mjs:25:32177) **Troubleshooting Steps Performed:** I have confirmed that the issue is not with the CrowdSec LAPI itself. 1. Networking between the pangolin and crowdsec containers is working. 2. A curl -v http://crowdsec:8080/v1/health from inside the pangolin container results in a 404 Not Found. 3. However, the CrowdSec LAPI is functional. The Traefik bouncer connects successfully, and a manually registered test-bouncer using cscli bouncers add also validates successfully, showing a ✔️ in cscli bouncers list. This proves the LAPI is working for standard bouncers, but the Pangolin application fails when it tries to communicate with it during Newt registration.
GiteaMirror added the stale label 2026-04-16 08:25:51 -05:00
Author
Owner

@oschwartz10612 commented on GitHub (Jun 15, 2025):

Hi! Thanks for posting your troubleshooting and logs!

This is caused by Pangolin not being able to address the Gerbil container actually. When newt connects it needs to add a peer to the wireguard server. Can you make sure you have deployed Gerbil and it is reachable from Pangolin within the docker network at the --reachableAt flag? If you need help feel free to post your docker compose.

I updated this error in ddd2924 to make it easier for people to know what is going on.

<!-- gh-comment-id:2974010980 --> @oschwartz10612 commented on GitHub (Jun 15, 2025): Hi! Thanks for posting your troubleshooting and logs! This is caused by Pangolin not being able to address the Gerbil container actually. When newt connects it needs to add a peer to the wireguard server. Can you make sure you have deployed Gerbil and it is reachable from Pangolin within the docker network at the --reachableAt flag? If you need help feel free to post your docker compose. I updated this error in [ddd2924](https://github.com/fosrl/pangolin/commit/ddd292422b52e1b061799247f9ca576489dfdc2c) to make it easier for people to know what is going on.
Author
Owner

@github-actions[bot] commented on GitHub (Jun 30, 2025):

This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.

<!-- gh-comment-id:3017344846 --> @github-actions[bot] commented on GitHub (Jun 30, 2025): This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
Author
Owner

@github-actions[bot] commented on GitHub (Jul 14, 2025):

This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.

<!-- gh-comment-id:3067434560 --> @github-actions[bot] commented on GitHub (Jul 14, 2025): This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#1688