Skip to content

Overview

Remnawave Reverse ProxyRemnawave Reverse Proxy

The script installs the Remnawave panel, a node and a reverse proxy on NGINX and Xray in one command. Xray runs directly on port 443 and hands traffic to NGINX through a Unix socket: with no extra TCP hops, connections come out faster and more reliable.

Single server

The panel and the Xray node live on one machine. Suits compact installations with moderate traffic: a single server covers everything.

Distributed

A panel server without a node and a separate node server with a SelfSteal stub for VLESS Reality. There can be as many nodes as you need, the panel is one.

At installation the script asks how to protect the panel. The default is a secret link:

https://panel.example.com/auth/login?<SECRET_KEY>=<SECRET_KEY>

The link sets a cookie in the browser, and without the correct pair the panel looks like a blank page. The two other options put a login page in front of the panel:

Cookie protection

The cookie name and value equal the secret key. Scanners do not detect the panel, path brute-forcing runs into a blank page.

ModedefaultWeb serverNGINX or CaddyWithout the keyblank page or 404

TinyAuth

A login page comes up on a separate subdomain in front of the panel: the script sets its login and password during installation.

Web serverNGINXLogin pageauth.your-domain

Caddy with MFA

The panel hides behind a login page with two-factor authentication: MFA is enabled after the first login.

Web serverCaddyImagecaddy-with-authLoginusername, password and an MFA code

Subscriptions

Client configurations update through the subscription: add a host in the panel, the client picks it up on its own.

JSONwith format conversion for popular clientsSubscription pageyour own, on your domain

NGINX and the socket

Xray takes port 443 and talks to NGINX through a Unix socket instead of a TCP loop.

Port 443Xray directlyLinkUnix socketEffectless TCP overhead

Security

The script’s base: the firewall, certificates and masking are configured at installation.

FirewallUFWCertificatesCloudflare or ACME, auto-renewalIPv6leak protectionTCPBBR algorithmMaskinga random site template

Everything above is what the script does at installation. Then come the modules: each opens from the main menu and is covered in detail on its own wiki page.

Node outbound traffic through Cloudflare WARP.

Torrent Blocker plus ingress and egress traffic filters.

Proxy host checks and a public status page.

Manage the whole fleet from one menu.

Node traffic through a bridge to a separate exit server.

Host groups with automatic switching in the Mihomo subscription.

Strict response rules: browsers, webviews and known clients.

A private network for the panel and nodes without public ports.

Panel backups and migration to a new server.

Found a problem

Open an issue in the repository or discuss it in the community Telegram chat.

Support the project

The project is free and developed in spare time. A donation funds future updates and improvements.

TON USDT