Skip to main content

2 posts tagged with "updating-guides"

View All Tags

Updating from to 1.5.x

· One min read
Remnawave
Remnawave
Maintainer

Warning​

danger

It is necessary to update the Remnawave Node (Remnanode) to v1.5.x AFTER updating the Remnawave Panel.

Remnawave Panel​

warning

Open you current Remnawave Panel in browser and logout.

1. Update Remnawave Panel​

docker compose pull && docker compose down && docker compose up -d && docker compose logs -f -t

2. Recreate admin user with RESCUE CLI​

1.5.x version of Remnawave Panel uses a new password hashing algorithm, so old admin user will not be able to login.

docker exec -it remnawave remnawave

After entering the Rescue CLI, select option 'Reset superadmin' and follow the instructions.

3. Open Remnawave Panel​

You will be prompted to create a new superadmin user.

4. Getting new SSL_CERT​

In Remnawave Dashboard, go to Nodes -> Management and copy new SSL_CERT.

5. Update Remnawave Node (Remnanode)​

Firstly, update SSL_CERT in the .env file with new one.

cd /opt/remnanode && nano .env

Then, update Remnawave Node (Remnanode) with command:

docker compose pull && docker compose down && docker compose up -d && docker compose logs -f -t

Updating from 1.3.x to 1.4.x

· 3 min read
Remnawave
Remnawave
Maintainer

Remnawave Panel​

Updating backend​

  1. Update docker-compose.yml.
cd /opt/remnawave && nano docker-compose.yml
  1. Replace your current configuration with the new one:
docker-compose.yml
services:
    remnawave-db:
        image: postgres:17
        container_name: 'remnawave-db'
        hostname: remnawave-db
        restart: always
        env_file:
            - .env
        environment:
            - POSTGRES_USER=${POSTGRES_USER}
            - POSTGRES_PASSWORD=${POSTGRES_PASSWORD}
            - POSTGRES_DB=${POSTGRES_DB}
            - TZ=UTC
        ports:
            - '127.0.0.1:6767:5432'
        volumes:
            - remnawave-db-data:/var/lib/postgresql/data
        networks:
            - remnawave-network
        healthcheck:
            test: ['CMD-SHELL', 'pg_isready -U $${POSTGRES_USER} -d $${POSTGRES_DB}']
            interval: 3s
            timeout: 10s
            retries: 3

    remnawave:
        image: remnawave/backend:latest
        container_name: 'remnawave'
        hostname: remnawave
        restart: always
        ports:
            - '127.0.0.1:3000:3000'
        env_file:
            - .env
        networks:
            - remnawave-network
        depends_on:
            remnawave-db:
                condition: service_healthy
            remnawave-redis:
                condition: service_healthy

    remnawave-redis:
        image: valkey/valkey:8.0.2-alpine
        container_name: remnawave-redis
        hostname: remnawave-redis
        restart: always
        networks:
            - remnawave-network
        volumes:
            - remnawave-redis-data:/data
        healthcheck:
            test: ['CMD', 'valkey-cli', 'ping']
            interval: 3s
            timeout: 10s
            retries: 3

networks:
    remnawave-network:
        name: remnawave-network
        driver: bridge
        external: false

volumes:
    remnawave-db-data:
        driver: local
        external: false
        name: remnawave-db-data
    remnawave-redis-data:
        driver: local
        external: false
        name: remnawave-redis-data
  1. Moving on to the .env file.
cd /opt/remnawave && nano .env
  1. Remove old .env variables:
SUB_SUPPORT_URL
SUB_PROFILE_TITLE
SUB_UPDATE_INTERVAL
SUB_WEBPAGE_URL
EXPIRED_USER_REMARKS
DISABLED_USER_REMARKS
LIMITED_USER_REMARKS
SUPERADMIN_PASSWORD
SUPERADMIN_USERNAME

Don't worry about the removed variables, they are moved to dashboard settings. Check out "Subscription Settings" section in dashboard.

Superadmin credentials now is stored in database and you will be prompted to create a superadmin account after updating.

  1. Add new .env variables:
### REDIS ###
REDIS_HOST=remnawave-redis
REDIS_PORT=6379
  1. Going live
docker compose pull && docker compose down && docker compose up -d && docker compose logs -f -t

About subscription templates​

In previous versions of Remnawave, you could can mount custom templates for Sing-box, Mihomo, and Stash with setup similar to this:

docker-compose.yml
volumes:
    - ./custom/configs/clash/stash_template.yml:/var/lib/remnawave/configs/stash/stash_template.yml
    - ./custom/configs/clash/clash_template.yml:/var/lib/remnawave/configs/clash/clash_template.yml
    - ./custom/configs/singbox/singbox_legacy.json:/var/lib/remnawave/configs/singbox/singbox_legacy.json
    - ./custom/configs/singbox/singbox_template.json:/var/lib/remnawave/configs/singbox/singbox_template.json

In v1.4.x, we've removed support of mounting custom templates from docker-compose.yml.

Now, you can only use templates from dashboard.
Check out new section in dashboard Templates.

Remnawave Node (Remnanode)​

  1. Update with command:
cd /opt/remnanode && docker compose pull && docker compose down && docker compose up -d && docker compose logs -f -t