⚠️ Preconditions
💿 Operating System
Debian 13
📦 Installation Method
Panel & Node
❔ Problem Description
When upgrading from version 2.8.0 to 3.2.0 using the standard built‑in script menu, the update process only partially completes. The docker-compose.yml file has the remnawave-backend image hardcoded to tag 2 (or 2.x.x), while remnanode is set to latest. As a result, the backend stays on the last 2.8.0 release, but the node is pulled as 3.0.0. The panel itself continues to run normally, but the node becomes completely non‑functional because the two components are now incompatible with each other
remnawave:
image: remnawave/backend:2
container_name: remnawave
...
remnanode:
image: remnawave/node:latest
container_name: remnanode
...
⚙️ Steps to Reproduce
- Start with a working installation of Remnawave version 2.8.0.
- Run the standard update script via the built‑in menu.
- Allow the script to pull the latest Docker images.
- After the script finishes, check the running containers:
- Observe that remnawave-backend remains on version 2.x.x (because its tag is hardcoded to 2 in docker-compose.yml).
- Observe that remnanode is updated to 3.x.x (because its tag is set to latest).
- Attempt to use the node (e.g., connect clients, check node status, or test the API).
- Notice that while the panel (backend) still works, the node fails to respond, connect, or handle any traffic due to the version mismatch and incompatible API/configuration changes
📎 Logs or Screenshots
No response
ℹ️ Additional Information
Additionally, 3.2.0 introduces breaking changes that are not applied to the panel (which remains on 2.x.x):
- Environment variables JWT_API_TOKENS_SECRET, SWAGGER_PATH, SCALAR_PATH, and IS_DOCS_ENABLED are removed.
- JWT_AUTH_SECRET is renamed to APP_SECRET.
Users are identified by numeric id instead of uuid, and many endpoints have changed (see full changelog)
💿 Operating System
Debian 13
📦 Installation Method
Panel & Node
❔ Problem Description
When upgrading from version 2.8.0 to 3.2.0 using the standard built‑in script menu, the update process only partially completes. The docker-compose.yml file has the remnawave-backend image hardcoded to tag 2 (or 2.x.x), while remnanode is set to latest. As a result, the backend stays on the last 2.8.0 release, but the node is pulled as 3.0.0. The panel itself continues to run normally, but the node becomes completely non‑functional because the two components are now incompatible with each other
⚙️ Steps to Reproduce
📎 Logs or Screenshots
No response
ℹ️ Additional Information
Additionally, 3.2.0 introduces breaking changes that are not applied to the panel (which remains on 2.x.x):
Users are identified by numeric id instead of uuid, and many endpoints have changed (see full changelog)