Hi everyone!
A fresh release for Remnawave version 2.3.x dropped tonight
Let’s briefly go over the important points that happened.
It is mandatory to update the versions of all nodes - if you updated the panel!
If you used my script - I recommend updating with it as well!
First of all, of course, you need to read the notes from the developer themselves:
Next, here are my brief observations and notes on important things.
Our API has changed again.
This time the changes affected responses to requests.
Shortening parameters in .env
HWID is no longer set in .env. This setting has fully moved to the panel itself.
You can find it here:
But again, provided you actually use it…
I personally do not use HWID restrictions for various objective reasons, and for now I have enough traffic restrictions.
APP_PORT and SSL_CERT are no longer supported
With the October release of version 2.2.2, the variables used to operate the node were renamed
APP_PORT → NODE_PORT
SSL_CERT → SECRET_KEY
But if you closely follow my posts on Telegram and use my scripts - then in the latest RemnaNode management script releases - from the collection:
Migrators will perform the necessary file edits in .env or docker-compose.yml if required.
The process looks roughly like this:
📊 Update Analysis:
────────────────────────────────────────
🔄 Update Available
Reason: New version downloaded via docker pull
🚀 New version already downloaded, proceeding with update...
🚀 Performing Update...
────────────────────────────────────────
📝 Step 4: Checking environment variables...
🔄 Starting Environment Variables Migration Check...
──────────────────────────────────────────────────
🔍 Detected configuration type: env_file
✅ .env file is up to date
No migration needed - all variables use new format:
• NODE_PORT (instead of APP_PORT)
• SECRET_KEY (instead of SSL_CERT)
──────────────────────────────────────────────────
📝 Step 5: Stopping running container...
[+] Running 1/1
✔ Container remnanode Removed 3.9s
✅ Container stopped
📝 Step 6: Image already updated during check
📝 Step 7: Starting updated container...
[+] Running 1/1
✔ Container remnanode Started 0.6s
✅ Container started
──────────────────────────────────────────────────
🎉 RemnaNode updated successfully!
📋 Update Summary:
Previous: 1e547196b46b
Current: 938efa434067
Created: 2025-12-07 19:46:04
Script: v3.6.1
Status: Running
The script successfully updates versions installed by my own script. I am not responsible for updates of other versions or manual changes and cannot guarantee that everything will update correctly.
Other updates
All other updates are already described in the developer’s log and I don’t see the point in duplicating them here.
From me, I would like to highlight a pleasant improvement: the node list can now be displayed as a table:
Remnawave Scripts by DigneZzZ
Just in case, here are the latest changes in the script collection:
Selfsteal
Updated and improved the selfsteal script:
If Nginx is installed, by default it uses the socket
It checks that a node is running and whether the volume is forwarded to /dev/shm/ where the socket lies
Can also be installed via port, using --tcp flag
Added additional checks to reduce errors in the script’s operation
Optimized nginx config
Note that the script is only a simplification of work.
and adapting it to work in all your infra conditions is quite challenging. Especially regarding path forwarding in the volume.
Installation and operation tested in tandem with my own remnanode script, which has also become adaptive, and supports using a socket from the selfsteal script (determines if a socket file exists in the system and forwards it into the container).
Instructions inside the script have also been updated.
Readme updated.
README-selfsteal.md
RemnaWave and RemnaNode
In the work of installers RemnaWave and RemnaNode, small fixes are also periodically introduced. But their main function is still installation and convenient management of the panel and nodes.
This month I will try to publish a set of all the main scripts I use on servers.
SHM and Remnawave integration
If you use these two systems and need a template for integrating them, you can contact me for a purchase.
If you previously purchased a template for version 2.1.x and above, you will receive an update template for free - but our correspondence about this should be preserved.
Paid services
If it suits you, you can request a turnkey installation of SHM + Remnawave with various configuration options and bot options.
Additionally you can purchase a cool bot dialogue template for SHM
Additionally you can purchase a Web-APP page for the user (instead of a bot dialogue) - ONLY FOR SHM INTEGRATION!!! - Not working standalone.