What is this?
X4G is a fast, modern gateway for tunneling VLESS over WebSocket and XHTTP, with a built-in HTTP proxy, a management dashboard, a Telegram admin bot, and shareable subscription pages for grouped configs.
X4G is a fast, modern gateway for tunneling VLESS over WebSocket and XHTTP, with a built-in HTTP proxy, a management dashboard, a Telegram admin bot, and shareable subscription pages for grouped configs.Is this a VPN client or a server I run myself?It is a server-side proxy/tunnel gateway that you deploy yourself (for example on Railway), not a client app; you then connect to it with any VLESS-capable client such as v2rayNG, NekoBox, or Streisand.
It is a server-side proxy/tunnel gateway that you deploy yourself (for example on Railway), not a client app; you then connect to it with any VLESS-capable client such as v2rayNG, NekoBox, or Streisand.How do I deploy this?Fork the repo on GitHub, then in Railway go to New Project → Deploy from GitHub repo and pick your fork; Railway builds and deploys it automatically, after which you enable a public domain for the service.
Fork the repo on GitHub, then in Railway go to New Project → Deploy from GitHub repo and pick your fork; Railway builds and deploys it automatically, after which you enable a public domain for the service.Do I need a Telegram bot token to use it?No, the Telegram admin bot is optional; you only need to set TELEGRAM_BOT_TOKEN and TELEGRAM_ADMIN_IDS if you want to manage configs from Telegram instead of the web dashboard.
No, the Telegram admin bot is optional; you only need to set TELEGRAM_BOT_TOKEN and TELEGRAM_ADMIN_IDS if you want to manage configs from Telegram instead of the web dashboard.Will my configs and settings survive a restart?Only if you attach a persistent Railway Volume to the DATA_DIR path (default /data); otherwise all state, including configs, stats, and the admin password, lives only in the current container and is wiped on redeploy or restart.
Only if you attach a persistent Railway Volume to the DATA_DIR path (default /data); otherwise all state, including configs, stats, and the admin password, lives only in the current container and is wiped on redeploy or restart.What transport protocols can VLESS run over here?X4G supports VLESS over WebSocket and two XHTTP modes (packet-up and stream-up), selectable individually per config.
X4G supports VLESS over WebSocket and two XHTTP modes (packet-up and stream-up), selectable individually per config.Can I limit traffic, speed, and concurrent users per link?Yes, each generated link can have its own traffic cap in KB/MB/GB, a bandwidth throttle in Mbps, a concurrent IP/user limit, and an automatic expiry in days.
Yes, each generated link can have its own traffic cap in KB/MB/GB, a bandwidth throttle in Mbps, a concurrent IP/user limit, and an automatic expiry in days.What is a sub group?A sub group bundles several configs into one public (optionally password-protected) page showing live status, usage, and QR codes for all of them, instead of a plain base64 subscription link.
A sub group bundles several configs into one public (optionally password-protected) page showing live status, usage, and QR codes for all of them, instead of a plain base64 subscription link.How do I log into the admin dashboard?Log in with the ADMIN_PASSWORD environment variable, which defaults to 'X4GKING' if you don't set your own.
Log in with the ADMIN_PASSWORD environment variable, which defaults to 'X4GKING' if you don't set your own.What are similar projects?CFNext, vodiwalker_panel, nyx, RVG, Open-Box, back4app-vless, SuperJinX, CF-Workers-TGProxy
CFNext, vodiwalker_panel, nyx, RVG, Open-Box, back4app-vless, SuperJinX, CF-Workers-TGProxyWhich topics is it in?proxy-server, telegram-bot, vless, qr-code, tunnel, anti-censorship, censorship-circumvention, vpn, websocket, http, encryption, proxy
proxy-server, telegram-bot, vless, qr-code, tunnel, anti-censorship, censorship-circumvention, vpn, websocket, http, encryption, proxy