Updating from 1.3.x to 1.4.x

Remnawave Panel

Updating backend

1. Update docker-compose.yml.

cd /opt/remnawave && nano docker-compose.yml

2. 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

3. Moving on to the .env file.

cd /opt/remnawave && nano .env

4. 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

6. 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