171 ·GitHub
What is this?
A Dockerfile that builds and deploys the 'Marzban-node' VPN node service on Railway, patching it at build time so it fits Railway's networking model instead of shipping a copied fork of the source.
A Dockerfile that builds and deploys the 'Marzban-node' VPN node service on Railway, patching it at build time so it fits Railway's networking model instead of shipping a copied fork of the source.Does this repo contain its own copy of the Marzban-node source code?No. The Dockerfile clones Gozargah/Marzban-node fresh at build time and applies two small patches (in the style of PasarGuard-Node) to make it Railway-compatible.
No. The Dockerfile clones Gozargah/Marzban-node fresh at build time and applies two small patches (in the style of PasarGuard-Node) to make it Railway-compatible.How do I deploy this on Railway?Fork the repo, create a new Railway service from it, then after deploy add the service's host and port to your Marzban panel under Node Settings as a new node.
Fork the repo, create a new Railway service from it, then after deploy add the service's host and port to your Marzban panel under Node Settings as a new node.Do I need an existing Marzban panel to use this node?Yes, you register the deployed node's host and port inside your existing Marzban panel's Node Settings; you also need a Railway account to host it.
Yes, you register the deployed node's host and port inside your existing Marzban panel's Node Settings; you also need a Railway account to host it.Is TLS enabled by default between the panel and this node?No, by default it runs a non-TLS REST mode (SERVICETLS=false) because Railway terminates TLS at the edge and the node is only reachable over Railway's private network, so no client certificate is required; you can switch to the more secure upstream TLS mode by setting SERVICETLS=true and SSLCLIENTCERTFILE.
No, by default it runs a non-TLS REST mode (SERVICETLS=false) because Railway terminates TLS at the edge and the node is only reachable over Railway's private network, so no client certificate is required; you can switch to the more secure upstream TLS mode by setting SERVICETLS=true and SSLCLIENTCERTFILE.How do I update to the latest Marzban-node release?Since the source is cloned fresh at build time, just trigger a new Deploy on Railway and it rebuilds against the newest upstream Marzban-node code — no manual file syncing needed.
Since the source is cloned fresh at build time, just trigger a new Deploy on Railway and it rebuilds against the newest upstream Marzban-node code — no manual file syncing needed.Can I deploy this somewhere other than Railway?The patches specifically rely on Railway's injected $PORT variable and its private-network TLS termination, so this image is built for Railway; running it elsewhere would mean recreating that environment or dropping the patches.
The patches specifically rely on Railway's injected $PORT variable and its private-network TLS termination, so this image is built for Railway; running it elsewhere would mean recreating that environment or dropping the patches.What is PasarGuard-Node, and why is it mentioned?PasarGuard-Node is the project whose patching approach this repo explicitly copies, applying the same style of small Railway-compatibility patches on top of the upstream Marzban-node source.
PasarGuard-Node is the project whose patching approach this repo explicitly copies, applying the same style of small Railway-compatibility patches on top of the upstream Marzban-node source.What are similar projects?Marzban, PasarGuard-Node, 3x-ui, MasterHttpRelayVPN-RUST, vodiwalker_panel, mtproto.zig, Xray-core, trojan
Marzban, PasarGuard-Node, 3x-ui, MasterHttpRelayVPN-RUST, vodiwalker_panel, mtproto.zig, Xray-core, trojanWhich topics is it in?iran, dockerfile, tunnel, infrastructure, deployment, tls, censorship-circumvention, vpn, sysadmin, encryption, proxy, cloud
iran, dockerfile, tunnel, infrastructure, deployment, tls, censorship-circumvention, vpn, sysadmin, encryption, proxy, cloud