Requirements

Before installing, prepare the server and the domains. Everything else the script does itself: Docker, certificates, the firewall and the panel setup.

Version support

Remnawave panel

Any 3.x branch fits: if the script meets an old panel, it warns at startup.

Minimum3.0.0Old panelwarning at startup

Script

The script checks for updates itself and shows a notice when a new release is out.

Current version3.8.4Update checkitem 12 of the main menu

System requirements

Remnawave Panel

The panel server: web interface, database and background jobs.

OSUbuntu or DebianRAM2 GB min, 4 GB recommendedCPU2 cores min, 4 cores recommendedDisk20 GB

Remnawave Node

The node runs Xray-core, so the requirements are lower than for the panel.

OSUbuntu or DebianRAM1 GB minCPU1 core min

If your hardware is weaker

Remnawave can run on smaller machines, but it is not recommended: some background processes are resource-hungry. Remnawave Node itself is modest, but Xray-core can eat a lot of CPU and RAM under load.

What to prepare

Root access

The installer runs as root.

Systemfresh installVirtualizationtested on KVM

Free ports

The web server and Xray take ports 80 and 443.

80, 443must stay free2222opened by the script, panel access only

Three domains or subdomains

The panel, the subscription page and the camouflage site (selfsteal).

Node A recordcreated by the script via APIDNS providersCloudflare, Gcore, Bunny.net

Domain setup

The script issues SSL certificates in two ways:

Cloudflare

The script manages DNS through the Cloudflare API.

Tokena Cloudflare API tokenRecordscreated automatically with the token

ACME

Direct integration with the DNS provider, without a separate API key.

Keynot needed

DNS configuration examples

Single server installation (panel + node together)

Record Type	Name	Value	Proxy Status
A	example.com	your_server_ip	DNS only
CNAME	panel.example.com	example.com	DNS only
CNAME	sub.example.com	example.com	DNS only
CNAME	node.example.com	example.com	DNS only

Tip

The node.example.com record is optional for SelfSteal: the root domain example.com works too.

Distributed installation (panel and node on different servers)

Record Type	Name	Value	Proxy Status
A	example.com	panel_server_ip	DNS only
CNAME	panel.example.com	example.com	DNS only
CNAME	sub.example.com	example.com	DNS only
A	node.example.com	node_server_ip	DNS only

When everything is ready

Run the installer on the server as root:

bash <(curl -Ls https://raw.githubusercontent.com/eGamesAPI/remnawave-reverse-proxy/refs/heads/main/install_remnawave.sh)

If GitHub is unreachable

Run the installer from the jsDelivr mirror:

bash <(curl -Ls https://cdn.jsdelivr.net/gh/eGamesAPI/remnawave-reverse-proxy@main/install_remnawave.sh)

After the first install the script adds itself the short alias rr: the menu opens with the remnawave_reverse command or just rr.

---

Installing Remnawave componentsEvery installation path: panel, node, both, subscription page and adding a node.