Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

build(docker): bump the amd64 Chrome for Testing to 156.0.8078.47

Yudhi Armyndharise9049fa4b57f
diff --git a/Dockerfile b/Dockerfile
index 03997d374..103a06f9e 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -254,7 +254,7 @@ RUN if [ "$TARGETARCH" = arm64 ]; then \
ln -s /usr/bin/chromium /usr/local/bin/puppeteer-chrome; \
else \
mkdir -p /opt/puppeteer && \
- PUPPETEER_CACHE_DIR=/opt/puppeteer ./node_modules/.bin/puppeteer browsers install '[email protected]' && \
+ PUPPETEER_CACHE_DIR=/opt/puppeteer ./node_modules/.bin/puppeteer browsers install '[email protected]' && \
chown -R openwa:openwa /opt/puppeteer && \
chrome_path=$(find /opt/puppeteer/chrome/linux*/chrome-linux64/chrome | head -n 1) && \
test -n "$chrome_path" && \
diff --git a/docs/11-operational-runbooks.md b/docs/11-operational-runbooks.md
index d095840ef..cf8762899 100644
--- a/docs/11-operational-runbooks.md
+++ b/docs/11-operational-runbooks.md
@@ -664,15 +664,15 @@ curl -H "X-API-Key: $API_KEY" http://localhost:2785/api/health
```
> Restoring `sessions/` is required, not optional, when the rollback crosses a browser major upgrade (on
-> amd64, 0.23.5 moved Chrome for Testing from 146 to 153; arm64 runs the chromium Debian shipped when each
-> image was built), and the backup must predate the first start on the newer image; a daily backup taken
-> after the upgrade does not qualify. An older Chrome silently deletes the IndexedDB of a profile a newer
-> Chrome has opened, which is where whatsapp-web.js keeps the WhatsApp login. The symptom: every
-> previously linked whatsapp-web.js session starts at a QR code instead of reconnecting, the log names no
-> cause (0.23.3 and 0.23.4 log only a generic `relink_required` warning), and upgrading again does not
-> bring the pairing back. Changing only the image tag, or `helm rollback` (which keeps the volume), skips
-> the restore and hits this. A session first paired on the newer image is not in that backup and must be
-> paired again either way. Baileys sessions are unaffected.
+> amd64, 0.23.5 moved Chrome for Testing from 146 to 153 and the release after 0.25.0 moves it to 156; arm64
+> runs the chromium Debian shipped when each image was built), and the backup must predate the first start
+> on the newer image; a daily backup taken after the upgrade does not qualify. An older Chrome silently
+> deletes the IndexedDB of a profile a newer Chrome has opened, which is where whatsapp-web.js keeps the
+> WhatsApp login. The symptom: every previously linked whatsapp-web.js session starts at a QR code instead
+> of reconnecting, the log names no cause (0.23.3 and 0.23.4 log only a generic `relink_required` warning),
+> and upgrading again does not bring the pairing back. Changing only the image tag, or `helm rollback`
+> (which keeps the volume), skips the restore and hits this. A session first paired on the newer image is
+> not in that backup and must be paired again either way. Baileys sessions are unaffected.
> Restoring `sessions/` **and** `baileys/` is likewise required when rolling back past 0.23.5, on either
> engine and either architecture. 0.23.5 renames each session's auth directory from the session name to
diff --git a/docs/12-troubleshooting-faq.md b/docs/12-troubleshooting-faq.md
index 237f46e05..d2074fbe7 100644
--- a/docs/12-troubleshooting-faq.md
+++ b/docs/12-troubleshooting-faq.md
@@ -501,7 +501,7 @@ custom container that drops the `XDG_CONFIG_HOME` / `XDG_CACHE_HOME` setup or th
**Cause D — Debian 12 OS Chromium SIGTRAP in non-root Pods.**
If `Code: null` happens on Kubernetes, and the host kernel logs or `dmesg` shows `Trace/breakpoint trap (core dumped)` with exit code 133, the underlying Debian 12 OS `chromium` package has crashed due to strict non-root or seccomp constraints (even with `--no-zygote` or `Unconfined` seccomp).
-_Fix:_ On amd64, do not use the `chromium` package from Debian's `apt` — it SIGTRAPs under strict non-root/seccomp. Instead, download Chrome for Testing via Puppeteer during the Docker build (`./node_modules/.bin/puppeteer browsers install '[email protected]'`) and point `PUPPETEER_EXECUTABLE_PATH` to it. (arm64 keeps Debian's `chromium`, which ships a native arm64 binary, by choice: Chrome for Testing publishes linux-arm64 builds only from 153, and the image has not moved arm64 to one.) The official `Dockerfile` implements this mixed approach.
+_Fix:_ On amd64, do not use the `chromium` package from Debian's `apt` — it SIGTRAPs under strict non-root/seccomp. Instead, download Chrome for Testing via Puppeteer during the Docker build (`./node_modules/.bin/puppeteer browsers install '[email protected]'`) and point `PUPPETEER_EXECUTABLE_PATH` to it. (arm64 keeps Debian's `chromium`, which ships a native arm64 binary, by choice: Chrome for Testing publishes linux-arm64 builds only from 153, and the image has not moved arm64 to one.) The official `Dockerfile` implements this mixed approach.
**Quick triage:** run `docker stats openwa-api`, click **Start**, and watch which resource spikes toward its
limit the instant before the failure — that tells you A vs B. If neither moves and you see the crashpad
@@ -530,14 +530,14 @@ reads like a Puppeteer bug and gives no hint that the profile is the cause — t
advisory when it detects this error, and the session's `lastError` (the message the dashboard shows on
the session card) carries a short form of it, so the pointer survives without reading the container log.
-**Rolling back to an older browser** does not raise this error. An older Chrome silently deletes the
-IndexedDB of a profile a newer Chrome has opened, and that is where whatsapp-web.js keeps the WhatsApp
-login: every previously linked session starts at a QR code instead of reconnecting, the log names no
-cause (0.23.3 and 0.23.4 log only a generic `relink_required` warning), and upgrading again does not bring
-the pairing back. On amd64 this follows a rollback from 0.23.5 or later (Chrome for Testing 153) to 0.23.4
-or earlier (146); on arm64, a rollback to an image built with an older Debian chromium major. Restoring
-`sessions/` from a backup taken before the first start on the newer image keeps the pairing (see the
-upgrade runbook's rollback in docs/11); without one, scan a new QR.
+**Rolling back to an older browser** does not raise this error. An older Chrome silently deletes the IndexedDB
+of a profile a newer Chrome has opened, and that is where whatsapp-web.js keeps the WhatsApp login: every
+previously linked session starts at a QR code instead of reconnecting, the log names no cause (0.23.3 and
+0.23.4 log only a generic `relink_required` warning), and upgrading again does not bring the pairing back. On
+amd64 this follows a rollback from the release after 0.25.0 (Chrome for Testing 156) to 0.25.0 or earlier, and
+from 0.23.5 or later to 0.23.4 or earlier (146); on arm64, a rollback to an image built with an older Debian
+chromium major. Restoring `sessions/` from a backup taken before the first start on the newer image keeps the
+pairing (see the upgrade runbook's rollback in docs/11); without one, scan a new QR.
**Fix:** delete the affected session's profile dir and start the session again to scan a new QR. The
profile cannot be salvaged — clearing only the cache subdirs (`Cache`, `GPUCache`, `Code Cache`, …) is
diff --git a/docs/14-migration-guide.md b/docs/14-migration-guide.md
index 71c587f68..b738369c0 100644
--- a/docs/14-migration-guide.md
+++ b/docs/14-migration-guide.md
@@ -1073,15 +1073,15 @@ flowchart TD
```
> [!WARNING]
-> A rollback across a browser major upgrade (on amd64, 0.23.5 moved Chrome for Testing from 146 to 153;
-> arm64 runs the chromium Debian shipped when each image was built) must restore `sessions/` from a backup
-> taken before the first start on the newer image, on both the full and the partial branch: a partial
-> rollback that merges data but keeps the current `sessions/` loses every whatsapp-web.js login. An older
-> Chrome silently deletes the IndexedDB of a profile a newer Chrome has opened, so each previously linked
-> whatsapp-web.js session starts at a QR code instead of reconnecting, the log names no cause (0.23.3 and
-> 0.23.4 log only a generic `relink_required` warning), and upgrading again does not bring the pairing
-> back.
-> A session first paired on the newer image is not in that backup and must be paired again either way.
+> A rollback across a browser major upgrade (on amd64, 0.23.5 moved Chrome for Testing from 146 to 153 and
+> the release after 0.25.0 moves it to 156; arm64 runs the chromium Debian shipped when each image was
+> built) must restore `sessions/` from a backup taken before the first start on the newer image, on both the
+> full and the partial branch: a partial rollback that merges data but keeps the current `sessions/` loses
+> every whatsapp-web.js login. An older Chrome silently deletes the IndexedDB of a profile a newer Chrome
+> has opened, so each previously linked whatsapp-web.js session starts at a QR code instead of reconnecting,
+> the log names no cause (0.23.3 and 0.23.4 log only a generic `relink_required` warning), and upgrading
+> again does not bring the pairing back. A session first paired on the newer image is not in that backup and
+> must be paired again either way.
> Baileys sessions are unaffected.
> [!WARNING]