HTTP Proxy Frontend for VPN

This project provides an HTTP proxy server that routes all network connections through our VPN service. It allows you to securely tunnel your traffic through the VPN by configuring your system or applications to use this proxy.

Features

• HTTP/HTTPS proxy support
• Automatic VPN connection management
• Rate limiting
• TLS encryption
• Redis-based session management
• Connection statistics monitoring
• Prometheus metrics export

Running the Service

Environment Variables

• ADDR: Server address (default: :30001)
• API_URL: API endpoint URL (default: https://api.bringyour.com)
• PLATFORM_URL: Platform WebSocket URL (default: wss://connect.bringyour.com)
• PROXY_ADDR: Proxy listener address (default: :10000)
• METRICS_ADDR: Prometheus metrics endpoint address (default: :9090)
• CERT_FILE: Path to TLS certificate file (required)
• KEY_FILE: Path to TLS private key file (required)
• REDIS_ADDR: Redis server address (required)
• REDIS_PASSWORD: Redis password (optional)
• REDIS_DB: Redis database number (default: 0)
• RATE_LIMIT_NETWORK_PER_MINUTE: Rate limit for network connections per minute (default: 5)

API Endpoints

Add Client

Creates a new proxy client connection.

POST /add-client
Content-Type: application/json

{
    "auth_code": "your-auth-code"
}

Response:

{
    "host": "proxy.example.com",
    "port": 10000
}

Get Status

Returns the current service status.

GET /status

Response:

{
    "version": "0.0.0",
    "config_version": "0.0.0",
    "status": "ok",
    "client_address": "192.168.1.100:12345",
    "host": "proxy-server-1"
}

Get Proxy Stats

Returns proxy connection statistics.

GET /proxy/stats

Response:

{
    "connections_open": 5,
    "total_connections_count": 100,
    "bytes_sent": 1024,
    "bytes_received": 2048
}

Security

• All connections are encrypted using TLS
• Rate limiting prevents abuse
• Authentication required for proxy access
• Session management via Redis
• Connection monitoring and statistics

Development

Requirements:

• Go 1.23 or later
• Redis server
• TLS certificate and private key

Build the service:

go build -o service .

Run tests:

go test ./...

Prometheus Metrics

The service exposes the following Prometheus metrics at /metrics endpoint:

Connection Metrics

• urnetwork_httproxy_active_connections: Current number of active proxy connections
• urnetwork_httproxy_total_connections: Total number of proxy connections made
• urnetwork_httproxy_bytes_sent_total: Total number of bytes sent through the proxy
• urnetwork_httproxy_bytes_received_total: Total number of bytes received through the proxy

Performance Metrics

• urnetwork_httproxy_request_duration_seconds: Histogram of request durations

Error Metrics

• urnetwork_httproxy_rate_limit_exceeded_total: Number of requests that exceeded rate limits
• urnetwork_httproxy_auth_failures_total: Number of authentication failures

Kubernetes Integration

The service includes a PodMonitor resource for automatic metric collection in Kubernetes environments with the Prometheus Operator:

# podmonitor.yaml
apiVersion: monitoring.coreos.com/v1
kind: PodMonitor
metadata:
  name: httproxy
  labels:
    app: httproxy
    release: prometheus
spec:
  selector:
    matchLabels:
      app: httproxy
  podMetricsEndpoints:
  - port: metrics
    path: /metrics
    interval: 30s

Apply the PodMonitor:

kubectl apply -f podmonitor.yaml

For non-Kubernetes environments, use this Prometheus configuration:

scrape_configs:
  - job_name: 'httproxy'
    static_configs:
      - targets: ['localhost:9090']