Skip to main content
This guide helps you diagnose and resolve common issues with NetBird deployments.

Quick Diagnostics

Check Client Status

Generate Debug Bundle

Create a comprehensive debug package with logs and system info:
The bundle includes:
  • Client logs
  • System information
  • Current status
  • Network configuration
  • Peer connection details
Debug bundles are saved as .tar.gz files in your current directory.

Run Timed Debug Session

Capture detailed logs for a specific duration:
This automatically:
  1. Sets log level to trace
  2. Restarts the connection
  3. Runs for the specified time
  4. Creates a debug bundle
  5. Restores original settings

Connection Issues

Peer Not Connecting

1

Check daemon status

2

Verify network reachability

3

Check firewall rules

4

Test with increased logging

NAT Traversal Failures

If peers can’t establish direct P2P connections:
  • Connections show as “Relayed” instead of “P2P”
  • High latency between peers
  • netbird status --detail shows relay connection type
  1. Verify STUN/TURN servers are accessible:
  2. Check symmetric NAT:
    • Symmetric NAT prevents direct P2P
    • Relay connection is expected behavior
  3. Configure external IP mapping:
  4. Open WireGuard port (51820/UDP):
  5. Verify relay server is running:

Authentication Failures

Error: status: StatusSessionExpired or StatusLoginFailedSolution:
Error: failed to connect to management serverDiagnosis:
Solutions:
  • Check firewall allows outbound HTTPS (443)
  • Verify DNS resolution
  • Check management server is running: docker compose ps management
  • Verify certificate validity
Error: Authentication redirects fail or timeoutCheck:
Common causes:
  • Incorrect IDP configuration in management.json
  • Network can’t reach IDP endpoints
  • IDP credentials expired or invalid

DNS Issues

NetBird DNS Not Resolving

1

Check DNS configuration

2

Test DNS resolution

3

Configure custom DNS resolver

DNS Resolution Conflicts

NetBird DNS may conflict with existing local DNS services on port 53.

Performance Issues

High Latency

Incorrect MTU can cause fragmentation and poor performance:

High CPU Usage

1

Check active connections

2

Profile CPU usage

3

Optimize connection settings

Service Issues

Service Won’t Start

Configuration File Issues

1

Locate config file

2

Validate JSON

3

Reset configuration

Server Issues

Management Server Not Starting

1

Check container status

2

Verify port availability

3

Check database connectivity

4

Validate configuration

High Memory Usage (Server)

Solutions:
  • Optimize peer groups and access rules
  • Consider splitting into multiple accounts
  • Increase container memory limits
Solutions:
  • Switch from SQLite to PostgreSQL for better concurrency
  • Reduce update frequency
  • Scale horizontally with multiple management instances

Network Configuration Issues

Interface Conflicts

Routing Issues

Firewall Blocking Peers

1

Check NetBird firewall rules

2

Verify peer access

3

Check ACL rules

Review access control rules in the NetBird dashboard

Getting Help

When seeking help, include:
  1. Debug bundle: netbird debug bundle --anonymize
  2. Client version: netbird version
  3. Operating system and version
  4. Deployment method: self-hosted, cloud, docker
  5. Error messages from logs
  6. Network topology (NAT types, firewalls)
Join the NetBird community:

Common Error Messages