Skip to content

Troubleshooting Guide

This comprehensive guide helps you diagnose and resolve issues with Bifrost Proxy. Use the quick diagnostics below to identify your issue, then navigate to the relevant section for detailed solutions.

Before diving into specific issues, run these diagnostic commands to assess the health of your Bifrost deployment.

Terminal window
# Server health status
curl http://localhost:7082/api/v1/health
# Server detailed status
curl http://localhost:7082/api/v1/status
# Backend health
curl http://localhost:7082/api/v1/backends
# Active connections
curl http://localhost:7082/api/v1/stats

For detailed diagnostic information, enable debug logging:

logging:
level: debug
format: text # Human-readable output

Or via CLI flag:

Terminal window
bifrost-server -c config.yaml --log-level debug

Select the category that best matches your issue:

Category Common Symptoms
Connection Issues Connection refused, timeouts, proxy errors
Performance High latency, slow responses, resource usage
Authentication Login failures, 407 errors, token issues
VPN & Tunnels Tunnel failures, routing problems, DNS issues
Diagnostics & Logs Log analysis, debugging commands, metrics
FAQ Frequently asked questions and quick answers
flowchart TD
    Start[Issue Detected] --> Q1{Can you connect<br/>to the proxy?}

    Q1 -->|No| Conn[Connection Issues]
    Q1 -->|Yes| Q2{Is authentication<br/>working?}

    Q2 -->|No| Auth[Authentication Issues]
    Q2 -->|Yes| Q3{Is traffic flowing<br/>correctly?}

    Q3 -->|No| Q4{Using VPN/tunnel<br/>backend?}
    Q3 -->|Yes| Q5{Performance<br/>acceptable?}

    Q4 -->|Yes| VPN[VPN & Tunnel Issues]
    Q4 -->|No| Conn

    Q5 -->|No| Perf[Performance Issues]
    Q5 -->|Yes| Done[System Working]

    click Conn "./connections" "Go to Connection Issues"
    click Auth "./authentication" "Go to Authentication Issues"
    click VPN "./vpn-tunnels" "Go to VPN & Tunnel Issues"
    click Perf "./performance" "Go to Performance Issues"

    style Start fill:#4a90e2,stroke:#2c5aa0,color:#fff
    style Done fill:#50c878,stroke:#3a9d5f,color:#fff
    style Conn fill:#ff6b6b,stroke:#cc5555,color:#fff
    style Auth fill:#ff6b6b,stroke:#cc5555,color:#fff
    style VPN fill:#ff6b6b,stroke:#cc5555,color:#fff
    style Perf fill:#ff6b6b,stroke:#cc5555,color:#fff

If your Bifrost deployment is completely unresponsive:

Terminal window
# Check if process is running
ps aux | grep bifrost
# Check systemd service status
systemctl status bifrost-server
# Check Docker container status
docker ps -a | grep bifrost
Terminal window
# Validate configuration file
bifrost-server validate -c config.yaml
# Check for YAML syntax errors
yamllint config.yaml
Terminal window
# Systemd logs
journalctl -u bifrost-server -n 100 --no-pager
# Docker logs
docker logs bifrost-server --tail 100
# File-based logs
tail -100 /var/log/bifrost/server.log
Terminal window
# Systemd
sudo systemctl restart bifrost-server
# Docker
docker restart bifrost-server
# Manual
pkill bifrost-server && bifrost-server -c config.yaml

If you cannot resolve your issue using this guide:

  1. Search existing issues - GitHub Issues
  2. Gather diagnostic information:
    • Bifrost version: bifrost-server version
    • Operating system and version
    • Configuration file (remove sensitive data)
    • Relevant log output
    • Steps to reproduce
  3. Open a new issue with the information above