boingbasti/nordvpn-socks5 repository overview

⁠SOCKS5 Proxy Docker Container

A secure, IPv4-only SOCKS5 proxy for Docker, designed to run behind a VPN gateway or as a standalone service.

⁠📦 Links

• Docker Hub: boingbasti/nordvpn-socks5⁠
• GitHub Repository: boingbasti/docker-nordvpn-socks5⁠

⁠✨ Features

• Minimal & Secure: Built using a multi-stage Docker build → tiny (~10 MB) Alpine-based image with minimal attack surface.
• Access Control:
  • Restrict access by IP address or subnet using ALLOWED_IPS.
  • Optional username + password authentication (PROXY_USER, PROXY_PASSWORD).
• Strictly IPv4:
  • Blocks all incoming requests from IPv6 clients.
  • Prevents outgoing connections to IPv6 destinations → no IPv6 leaks.
• Easy Configuration: Fully managed via environment variables.
• Informative Logging: Clear logs for allowed connections, blocked attempts, and errors.

⁠🛠 Requirements

• Docker installed on your host system.

⁠📦 Environment Variables

⁠🚀 Usage

⁠1. Standalone Mode

Run the SOCKS5 proxy directly and expose it to your host machine.

services:
  socks5-proxy:
    image: boingbasti/nordvpn-socks5:latest
    container_name: socks5-proxy
    ports:
      - "1080:1080"
    environment:
      # Allows access from the whole 192.168.1.0/24 subnet
      - ALLOWED_IPS=192.168.1.0/24
      # Optional authentication
      # - PROXY_USER=myuser
      # - PROXY_PASSWORD=mypassword
    restart: unless-stopped

➡️ Clients can now connect to the proxy at HOST_IP:1080.

⁠2. VPN Gateway Mode (Recommended)

Attach the proxy to a VPN gateway container (e.g., docker-nordvpn-gateway⁠) so all traffic is routed through the VPN tunnel.

# In your existing docker-compose.yml with the vpn-gateway service...
services:
  vpn-gateway:
    # ... your vpn-gateway configuration ...

  socks5-proxy:
    image: boingbasti/nordvpn-socks5:latest
    container_name: nordvpn-socks5
    # Shares the VPN gateway’s network stack
    network_mode: "service:vpn-gateway"
    depends_on:
      - vpn-gateway
    environment:
      - PROXY_PORT=1080
      - ALLOWED_IPS=192.168.1.0/24
    restart: unless-stopped

➡️ Clients should connect to the VPN gateway’s LAN IP (e.g., 192.168.1.240:1080).

⁠🔍 Troubleshooting

• Connection refused / not working

  • Ensure the client’s IP is included in ALLOWED_IPS.
  • In standalone mode, confirm port mapping (1080:1080).

• Authentication error

  • Both PROXY_USER and PROXY_PASSWORD must be set.

• Blocked IPv6 log messages

  • This is intentional. The proxy is strictly IPv4-only.