What is this?
This is a Railway deployment setup for the 3x-ui panel that adds an nginx reverse proxy so both the web panel and a VLESS/WebSocket inbound are reachable through the single port Railway assigns to your deployment.
This is a Railway deployment setup for the 3x-ui panel that adds an nginx reverse proxy so both the web panel and a VLESS/WebSocket inbound are reachable through the single port Railway assigns to your deployment.Is this 3x-ui itself or just a deployment wrapper around it?It is a wrapper around 3x-ui: the repo ships a Dockerfile, an nginx.conf.template, and a start.sh script that run 3x-ui alongside nginx, routing panel and inbound traffic to the same exposed port.
It is a wrapper around 3x-ui: the repo ships a Dockerfile, an nginx.conf.template, and a start.sh script that run 3x-ui alongside nginx, routing panel and inbound traffic to the same exposed port.How do I deploy this on Railway?Push the Dockerfile, nginx.conf.template and start.sh to a new GitHub repo, then in Railway choose New Project then Deploy from GitHub repo and pick that repo; Railway auto-detects the Dockerfile and builds it, after which you generate a domain under Settings then Networking (no specific target port needed since nginx listens directly on $PORT).
Push the Dockerfile, nginx.conf.template and start.sh to a new GitHub repo, then in Railway choose New Project then Deploy from GitHub repo and pick that repo; Railway auto-detects the Dockerfile and builds it, after which you generate a domain under Settings then Networking (no specific target port needed since nginx listens directly on $PORT).What do I need before deploying this?You need a GitHub repository (private or public) containing the three provided files and a Railway project connected to that repo; no extra tools are required beyond that.
You need a GitHub repository (private or public) containing the three provided files and a Railway project connected to that repo; no extra tools are required beyond that.What should I watch out for after deploying?All inbounds must listen on the fixed internal port 8080 because nginx only proxies that one port, and panel data under /etc/x-ui lives on the container's temporary filesystem - it gets wiped on redeploy unless you attach a Railway Volume to that path.
All inbounds must listen on the fixed internal port 8080 because nginx only proxies that one port, and panel data under /etc/x-ui lives on the container's temporary filesystem - it gets wiped on redeploy unless you attach a Railway Volume to that path.What's the default panel login, and should I change it?The default 3x-ui credentials are admin/admin, and the README stresses that you should change them immediately from the settings section right after first login.
The default 3x-ui credentials are admin/admin, and the README stresses that you should change them immediately from the settings section right after first login.Why not just run 3x-ui directly on Railway without this nginx layer?3x-ui normally serves its panel and each inbound on separate ports, but Railway's Public Domain only forwards a single internal port - without this nginx wrapper you could only reach the panel or the proxy inbound, never both.
3x-ui normally serves its panel and each inbound on separate ports, but Railway's Public Domain only forwards a single internal port - without this nginx wrapper you could only reach the panel or the proxy inbound, never both.Can I create more than one VLESS inbound this way?Yes, as long as every inbound listens on the same internal port 8080; different inbounds can use different WebSocket paths since nginx only distinguishes them by path, not by TCP port.
Yes, as long as every inbound listens on the same internal port 8080; different inbounds can use different WebSocket paths since nginx only distinguishes them by path, not by TCP port.What are similar projects?SuperJinX, nyx, v2ray-agent, back4app-vless, marzban-node, bot-hosting-vless, personal-edge-proxy, CFNext
SuperJinX, nyx, v2ray-agent, back4app-vless, marzban-node, bot-hosting-vless, personal-edge-proxy, CFNextWhich topics is it in?vpn-server, xray-core, admin-panel, dockerfile, vless, nginx, v2ray, tunnel, self-hosting, reverse-proxy, deployment, vpn
vpn-server, xray-core, admin-panel, dockerfile, vless, nginx, v2ray, tunnel, self-hosting, reverse-proxy, deployment, vpn