Panel and subscription page

Running the script

Run this command on your server:

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

Installing the panel and subscription page

What the installer does

Checks the server before starting: the panel is not installed yet, port 443 is free.
Asks for two domains: the panel’s and the subscription page’s. Each is validated and its DNS record is checked, and the two must be different.
Generates every secret itself: the superadmin login and password, the name=value pair for the secret login link, a separate metrics pair and APP_SECRET: everything is shown at the end.
Deploys the services into /opt/remnawave: the PostgreSQL database, the Valkey cache, the RemnaWave panel, a reverse proxy and the subscription page container, which pulls its configuration straight from the panel via an API token.
Issues Let’s Encrypt certificates for both domains using the method you pick (DNS API, ACME HTTP-01 or your own) and sets up renewal.
Configures the panel through its API: registers the superadmin and issues a token for the subscription page.
Restarts the stack cleanly (down + up), subscription page included: if something did not come up, the error cannot hide behind the green banner.

Step-by-step installation

Select Install Remnawave Components

root@server: ~

REMNAWAVE REVERSE-PROXY by eGames
Version: 3.8.4
Wiki: https://wiki.egam.es/

1.Install Remnawave Components
2.Reinstall Panel and Components
3.Manage Panel and Components

4.Node extensions (templates, plugins, core)
5.Subscriptions: rules and page

6.WARP Native
7.Backup and restore

8.Xray Checker — subscription monitoring
9.NetBird: overlay network for nodes and panel

10.Manage IPv6
11.Manage certificates domain

12.Check for updates script
13.Remove script
0.Exit
- Quick start: remnawave_reverse (or rr)

Select action (0-13):

Then select Install panel and subscription page

root@server: ~

Install Remnawave Components

1.Install panel and node on one server
2.Install panel and subscription page
3.Add node to panel
4.Install only the node
5.Install only the panel
6.Install only the subscription page

0.Exit

Select action (0-6):

Select the web server for the panel:
- Nginx: the classic scheme used in all previous versions.
- Caddy: automatic HTTPS certificates out of the box.
root@server: ~
```
Select web server:

1.Nginx
2.Caddy

0.Exit

Select action (0-2):
```
Enter the two domains when asked: the panel’s and the subscription page’s
root@server: ~
```
Enter panel domain (e.g. panel.example.com): panel.example.com
Enter subscription domain (e.g. sub.example.com): sub.example.com
```
If the domain’s A record does not point at this server yet, the script offers to create it automatically through the Cloudflare or Gcore API, or you create it manually and the script checks the record again.
Select the panel protection method:
- Nginx
- Caddy
1. Cookie protection (default): the panel is hidden behind a secret link, as in previous versions.
2. Login page (TinyAuth): an extra login page in front of the panel.
root@server: ~
```
Panel protection method:

1.Cookie protection (default)
2.Login page (TinyAuth)

Select action (1-2):
```
1. Cookie protection (default): the panel is hidden behind a secret link, as in previous versions.
2. Login page with MFA: a login portal with multi-factor authentication in front of the panel.
root@server: ~
```
Panel protection method:

1.Cookie protection (default)
2.Login page with MFA

Select action (1-2):
```
When the MFA portal is enabled, set up MFA for the administrator after the first login.

Select the certificate generation method for both domains:

root@server: ~

Select certificate generation method for all domains:

1.Cloudflare DNS API
    Wildcard, DNS records are created automatically via an API key
2.Gcore DNS API
    Wildcard, DNS records are created automatically via an API key
3.Bunny.net DNS API
    Wildcard, DNS records are created automatically via an API key

4.ACME HTTP-01
    No API key, one domain per certificate

5.Install your own certificate
    Upload your own fullchain.pem and privkey.pem

0.Exit

Select action (0-5):

If you chose Let’s Encrypt, enter the email for certificate notifications, or just press Enter to skip
root@server: ~
```
Enter your Let's Encrypt email (or press Enter to skip):
```
From here the script works on its own: it writes the services into /opt/remnawave, configures the panel through the API and restarts everything cleanly, subscription page included
root@server: ~
```
Installing panel
[ * ] Checking containers availability...
[ * ] Stopping Remnawave Subscription Page...
[ * ] Starting Remnawave Subscription Page...
```

When the installation finishes, the script prints everything you need to log into the panel

root@server: ~

=================================================
               INSTALLATION COMPLETE!
=================================================
Panel URL:
https://panel.example.com/auth/login?zIdejKtN=MWbLrRzx
-------------------------------------------------
To log into the panel, use the following data:
Username: admin
Password: k7XmQ2vLpR9t
-------------------------------------------------
To relaunch the manager, use the following command:
remnawave_reverse
=================================================
The node is added once the panel is up: run this script on the panel server, select 'Install Remnawave Components', then 'Add node to panel'.

When the installation finishes, the script shows a unique login URL for the panel.
Save this URL. It contains the secret key required for access.

Example login link:

https://p.example.com/auth/login?zIdejKtN=MWbLrRzx

How it depends on the protection method:

Cookie protection — default

The secret link is the only way in. Without it the panel is invisible: a scanner sees an empty page or a 404.

A login page opens in front of the panel. The final screen shows its address together with the username and password instead of the secret link.

MFA portal — Caddy

Login goes through a portal with multi-factor authentication. After the first login, set up MFA for the administrator: without it the next login will not pass.

Updating the script

Make sure the script is up to date before you do anything else with it.

Open the script menu with the remnawave_reverse command (or the short alias rr) and select item 12, Check for updates script. When an update is already found, the item lights up red and reads Update script:
root@server: ~
```
REMNAWAVE REVERSE-PROXY by eGames
Version: 3.8.4 script update available
…
9.NetBird: overlay network for nodes and panel
13.Update script
13.Remove script

0.Exit

Select action (0-13):
```
What changed in each version is on the releases page:

View the latest release