This 3x-ui project packages the 3x-ui panel with an Nginx reverse proxy for deployment on Railway through a single public port. Standard 3x-ui setups use separate ports for the web panel and proxy inbounds, which conflicts with Railway’s one-port routing model. Nginx listens on Railway’s assigned port and routes the management panel and VLESS WebSocket traffic through different URL paths. The included Dockerfile, configuration template, and startup script provide a compact deployment workflow. Users create a VLESS inbound on the expected internal port and connect through the generated Railway domain with TLS. Multiple WebSocket paths can share that internal port, allowing several inbound configurations behind one endpoint. A Railway volume can preserve panel settings, users, and inbound data across container redeployments.
Features
- Single-port Railway deployment
- Nginx reverse proxy routing
- 3x-ui management panel access
- VLESS WebSocket inbound support
- Docker-based automated startup
- Persistent Railway volume support