What is this?
This repo deploys a 'PasarGuard Node' (a node for the PasarGuard proxy panel) as a second Railway service, with a self-signed TLS certificate baked into the Docker image at build time, so you don't need a separate VPS just to get a Server CA for the panel.
This repo deploys a 'PasarGuard Node' (a node for the PasarGuard proxy panel) as a second Railway service, with a self-signed TLS certificate baked into the Docker image at build time, so you don't need a separate VPS just to get a Server CA for the panel.Is this a library or just a deployment template?It is a deployment template: a Docker image plus Shell scripts that you push to your own GitHub repo and deploy as a Railway service, not a package you install into code.
It is a deployment template: a Docker image plus Shell scripts that you push to your own GitHub repo and deploy as a Railway service, not a package you install into code.How do I get this node running?Push this folder to its own GitHub repo, create a new Railway service from that repo in the same Railway project as your PasarGuard panel, set an APIKEY variable to a UUID you generate, enable TCP Proxy on port 62050 in that service's Networking settings, and deploy.
Push this folder to its own GitHub repo, create a new Railway service from that repo in the same Railway project as your PasarGuard panel, set an APIKEY variable to a UUID you generate, enable TCP Proxy on port 62050 in that service's Networking settings, and deploy.Do I need a VPS or just Railway?You need a Railway account and an already-running PasarGuard panel (deployed as the first service in the same Railway project); no external VPS is required for TLS.
You need a Railway account and an already-running PasarGuard panel (deployed as the first service in the same Railway project); no external VPS is required for TLS.What steps can't be skipped?You must manually enable TCP Proxy and point it at target port 62050 in Railway's Networking settings, then copy the generated certificate from the service console into the panel's 'Server CA' field - missing either step leaves the node unreachable.
You must manually enable TCP Proxy and point it at target port 62050 in Railway's Networking settings, then copy the generated certificate from the service console into the panel's 'Server CA' field - missing either step leaves the node unreachable.What is the PasarGuard panel this node connects to?It's a separate proxy panel service (deployed as the first Railway service) that this node registers with, using the Address, Port, API Key, and Server CA it provides.
It's a separate proxy panel service (deployed as the first Railway service) that this node registers with, using the Address, Port, API Key, and Server CA it provides.Why bake a self-signed certificate into the image instead of using a real one?It lets the node obtain a usable Server CA for the panel without renting or configuring an external server with a public domain and TLS setup.
It lets the node obtain a usable Server CA for the panel without renting or configuring an external server with a public domain and TLS setup.What is the APIKEY variable used for?It's a UUID you generate yourself that acts as the shared secret between the panel and this node, entered both as the Railway variable and as the API Key when adding the node in the panel.
It's a UUID you generate yourself that acts as the shared secret between the panel and this node, entered both as the Railway variable and as the API Key when adding the node in the panel.What are similar projects?v2ray, nyx, v2ray-agent, personal-edge-proxy, Marzban, back4app-vless, marzban-node, Xray-core
v2ray, nyx, v2ray-agent, personal-edge-proxy, Marzban, back4app-vless, marzban-node, Xray-coreWhich topics is it in?xray, v2ray, anti-censorship, deployment, tls, censorship-circumvention, vpn, authentication, encryption, shell, proxy, cloud
xray, v2ray, anti-censorship, deployment, tls, censorship-circumvention, vpn, authentication, encryption, shell, proxy, cloud