Telegram VPN Module Development with Custom Backend Integration

├── :443 mtproto-proxy (nineseconds/mtg:2, simulatedTLS, cloudflare.com)
├── :8443 mtg-member (ghcr.io/mhsanaei/mtg-multi:latest, )
│ └── :9090 ( 127.0.0.1) API + bearer token
├── :8080 mtproto-webui (python:3.11-slim, FastAPI 0.109.0 + uvicorn 0.27.0 + Jinja2 3.1.3)
├── :32662 mtproto-proxy-node_fd9248 (mtg:2, vultr.com) ←
├── :21691 mtproto-proxy-node_2ee68c (mtg:2, digitalocean.com) ←
└── systemd: mtg-bot.service (python3 /opt/mtg-bot/bot.py, @laosha689bot)
: /opt/mtprotoserver/docker-compose.yml (compose v3.8, docker-compose v1 , compose ) .
/ , MySQL / redis:

: Telegram ( / ) , ( , , ) . Telegram , , .

: 7 , , , , CPU .
: , ” 30GB”” “, .
: , , , .
: , , .
: , .
, ( )
, .
( http https, ) , ” “.
, , .
” , “, .
: , , , .

#tg #telegram # vpn #mtproto-proxy #MTProto