A Docker-based SOCKS5 proxy server with user management and Telegram bot administration.
Socks5 proxy server is a Docker-based SOCKS5 proxy implementation that provides secure network proxying with user authentication and management. It solves the problem of deploying and managing a proxy server with minimal configuration, offering remote administration via a Telegram bot. The project simplifies proxy server operations through containerized deployment and scriptable user controls.
Developers and system administrators who need a self-hosted SOCKS5 proxy for testing, privacy, or network routing purposes, especially those familiar with Docker and CLI tools.
Developers choose this for its straightforward Docker setup, integrated Telegram bot for remote management, and scriptable user controls, making it easier to deploy and maintain compared to manual proxy server configurations.
SOCKS5 proxy server
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Setup is streamlined with Docker Compose; the README shows just copying .env.example and running docker compose up -d for quick deployment.
Telegram bot allows user creation, deletion, and stats viewing through commands like /create_user and /users_stats, enabling administration from anywhere.
CLI scripts such as create-user.js and delete-user.js facilitate automation, as demonstrated in the README for managing users via Docker exec commands.
REQUIRE_AUTH setting in .env lets you disable anonymous access, adding a basic layer of security as per the configuration instructions.
CLI commands require manually finding and specifying the container name with docker compose ps, adding overhead and potential for errors in administration.
Using webhooks for the Telegram bot necessitates SSL certificates, which the README mentions but doesn't detail, making it more involved than polling mode.
Only supports SOCKS5; lacks built-in features for other proxy types like HTTP or advanced security measures such as traffic encryption.
Usage statistics via CLI or Telegram are per user but lack detailed analytics, export options, or historical data, as indicated in the simple scripts.