Xray Manager

A Flask web app to parse and deploy V2Ray/Xray proxy configurations into a single Xray Docker container using multiple inbounds — one SOCKS5 port per proxy, all within one container.

• Python 3.11+
• Docker + Docker Compose v2 (docker compose command)
• The Docker socket accessible to the running user (for SIGHUP hot-reload)

docker compose up -d

Open http://localhost:65000

The app image is published as mparvin/xray-manager:latest.

pip install -r requirements.txt
python app.py
# then start the Xray container separately:
docker compose up -d xray

All proxies share a single Xray container (teddysun/xray:26.6.1). configs/config.json holds every proxy as a separate inbound + outbound pair connected by a routing rule.

When a proxy is deployed or removed the Flask app:

1. Updates configs/config.json (adds/removes the inbound, outbound, and routing rule)
2. Sends SIGHUP to the Xray process — hot-reloads the config with zero downtime for other proxies

A combined SOCKS proxy on port 1080 routes traffic through all deployed proxies using Xray's leastPing balancer and observatory health checks.

• Parse: Paste any raw text (Telegram message, config list, etc.) — the app extracts all ss://, vmess://, vless://, and trojan:// URIs automatically
• JSON import: Paste a full Xray/V2Ray client JSON config — proxy outbounds (vmess / vless / shadowsocks / trojan) are extracted; DNS/routing/inbounds from the paste are ignored
• Subscription import: Paste http(s):// subscription URLs in the same box — the app fetches them and parses plain URI lists or base64-encoded payloads
• Preview & Select: Review extracted proxies and select which ones to deploy
• Deploy: Each selected proxy gets:
  • An inbound entry (SOCKS5, unique port 62500–62999) added to configs/config.json
  • A matching outbound + routing rule added in the same file
  • Xray config hot-reloaded via SIGHUP (no container restart)
• Combined proxy: SOCKS5 on port 1080 with leastPing load balancing across all proxies
• Status Panel: Live status of all configured proxies with auto-refresh every 15s
• Latency: Connection time in milliseconds shown per proxy (measured through its SOCKS inbound)
• Reload button: Manually send SIGHUP to hot-reload Xray config
• Remove: Per-proxy removal — updates config and hot-reloads Xray
• Bulk actions: Remove duplicates, remove not-working proxies, export all configs
• API + Swagger: JSON API documented at /apidocs

configs/config.json is managed automatically and looks like:

{
  "log": { "loglevel": "warning" },
  "inbounds": [
    {
      "tag": "inbound-abc12345",
      "port": 62500,
      "listen": "0.0.0.0",
      "protocol": "socks",
      "settings": { "auth": "noauth", "udp": true }
    }
  ],
  "outbounds": [
    {
      "tag": "outbound-abc12345",
      "protocol": "vmess",
      "settings": { "vnext": [{ "address": "...", "port": 443, "users": [...] }] }
    },
    { "protocol": "freedom", "tag": "direct" }
  ],
  "routing": {
    "rules": [
      { "type": "field", "inboundTag": ["inbound-abc12345"], "outboundTag": "outbound-abc12345" }
    ]
  }
}

docker compose up -d          # start everything
docker compose logs xray -f   # follow Xray logs
docker compose restart xray   # full restart (if SIGHUP is not enough)

Pushes to main and version tags (v*) build and publish the app image to Docker Hub.

Repository: mparvin/xray-manager

Required GitHub secrets:

All proxies run inside a single teddysun/xray:26.6.1 container.

Interactive OpenAPI docs (Swagger UI): http://localhost:65000/apidocs/

Key endpoints:

• Shadowsocks support
• Trojan config support
• Connection time in milliseconds for each configuration
• JSON configuration import (extracts proxy outbounds from Xray/V2Ray configs)
• Subscription import (http/https URLs; plain or base64 bodies)
• API
• Swagger (/apidocs)