Redeploying WAHA deletes all sessions and configurations

[vd123D]

After redeploying the WAHA Plus container or updating it, all my previous WhatsApp sessions and configuration settings are getting completely deleted.

Every time I run a redeploy or update, it behaves as if it’s a fresh installation, forcing me to re-scan all WhatsApp QR codes and reconfigure everything manually.

This is a serious issue because:

It causes loss of all active sessions.

It disrupts ongoing business automation and integrations.

Even configuration files that were previously set are reset to default.

🧩 Reproducible Behavior

Deploy WAHA Plus using Docker (as usual).

Connect one or more WhatsApp sessions.

Redeploy the container using the same configuration (e.g., docker-compose up -d --build).

After redeployment, all sessions and settings are missing — the system starts clean again.

⚠️ Expected Behavior

WAHA Plus should retain sessions and configurations after redeployment or container restart — especially since this is a premium version.

💬 Note

This issue makes WAHA unstable for production use because redeploying for updates or bug fixes results in total data loss.
Please verify if this is a known issue or if persistent storage is not functioning as expected in the latest build.

[devlikepro]

Follow the guide and use the docker-compose.yaml from it
https://waha.devlike.pro/docs/how-to/install/
or connect the storage properly
https://waha.devlike.pro/docs/how-to/storages/

https://waha.devlike.pro/docs/how-to/storages/#quick-start

---

To use local storage with session persistence, you need to mount a volume to the /app/.sessions directory.

Here are the common ways to do this:

1. Using Docker Run (recommended for development):

    docker run -v `pwd`/.sessions:/app/.sessions -p 3000:3000 devlikeapro/waha-plus

2. Using Docker Compose (recommended for production):

services:
  waha:
    image: devlikeapro/waha-plus
    volumes:
      - ./.sessions:/app/.sessions
    ports:
      - "127.0.0.1:3000:3000"