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