[GH-ISSUE #3302] Unable to troubleshoot posture checks #7103

Open
opened 2026-08-05 01:11:35 -04:00 by saavagebueno · 2 comments
Owner

Originally created by @cristianrz on GitHub (Feb 8, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/3302

Describe the problem

I am struggling to figure out how to troubleshoot posture checks. Sometimes I will change a check and some clients will disconnect but I can't see anything in the server or client logs. Need to play with the checks for a while until I figure out what is going on.
To Reproduce

Steps to reproduce the behavior:

  1. Change posture checks
  2. Check activity log, server logs (all containers) and netbird log file.

Expected behavior

Somewhere I can see "device X failed Y posture check".

Are you using NetBird Cloud?

Self hosted.

NetBird version

0.36.5

Originally created by @cristianrz on GitHub (Feb 8, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/3302 **Describe the problem** I am struggling to figure out how to troubleshoot posture checks. Sometimes I will change a check and some clients will disconnect but I can't see anything in the server or client logs. Need to play with the checks for a while until I figure out what is going on. **To Reproduce** Steps to reproduce the behavior: 1. Change posture checks 2. Check activity log, server logs (all containers) and netbird log file. **Expected behavior** Somewhere I can see "device X failed Y posture check". **Are you using NetBird Cloud?** Self hosted. **NetBird version** 0.36.5
saavagebueno added the UXagentposture-checks labels 2026-08-05 01:11:35 -04:00
Author
Owner

@aschubert commented on GitHub (Apr 2, 2025):

What I find worse: on the client side is no notification of a failed posture check, so a user doesn't know, why it's not working. A little error message would be very helpful. So one could use a posture check on the client version to remind users to update to a newer version (as long as there is no auto update feature, but that's another point).

<!-- gh-comment-id:2772031714 --> @aschubert commented on GitHub (Apr 2, 2025): What I find worse: on the client side is no notification of a failed posture check, so a user doesn't know, why it's not working. A little error message would be very helpful. So one could use a posture check on the client version to remind users to update to a newer version (as long as there is no auto update feature, but that's another point).
Author
Owner

@NDebx commented on GitHub (May 4, 2026):

I agree, posture checks accidently blocked local DNS resolving. It's a great feature but would be nice to monitor it and build the posture checks to your own specific needs :(

<!-- gh-comment-id:4374413494 --> @NDebx commented on GitHub (May 4, 2026): I agree, posture checks accidently blocked local DNS resolving. It's a great feature but would be nice to monitor it and build the posture checks to your own specific needs :(
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#7103