Zero-touch runtime, browser preparation, repair and recovery

WhatsApp Web Messaging

Britixo WhatsApp Enterprise: complete how-to guide

Understand zero-touch runtime preparation

See how the CRM prepares the account-specific connector without exposing technical runtime fields.

Understand the private Node.js connector

Review the local service that owns the linked-device client, event store, media exchange and WhatsApp Web browser session.

Understand the Node.js version check

Know that preparation validates a suitable Node.js runtime and prefers version 20.11 or newer.

Understand bundled and system runtime fallbacks

See how the runtime manager tries safe PHP process-launch methods and available runtime locations before queueing a retry.

Understand Chromium browser discovery

Review how the connector resolves a usable private or system Chromium/Chrome binary and reports a preparation error if none is available.

Understand private browser fallback

Know that the installer can prepare a module-owned browser runtime when a suitable system browser is unavailable.

Understand loopback-only binding

Confirm the connector binds to 127.0.0.1 and is not intended to be exposed as a public remote service.

Understand remote connector protection

Know that the installed default disallows remote connector endpoints and normal settings do not offer an override.

Understand account-isolated runtime directories

See why each account has its own managed runtime, authentication and event-store paths.

Understand the runtime watchdog

Know that an administrator-page hook runs at most once per minute and restarts prepared connectors after server/process restarts.

Understand stalled-startup recovery

See how a bounded watchdog restarts a genuinely stalled INITIALISING state instead of leaving it indefinitely.

Understand launch-method fallbacks

Review the managed alternatives used when a hosting environment disables a preferred PHP process-launch function.

Understand queued preparation fallback

Know that a preparation request can be queued for cron when the web request cannot complete the runtime launch immediately.

Understand automatic build upgrades

See how the runtime build marker triggers managed connector-file refresh while preserving the linked-device session.

Repair missing runtime files

Use Connect/repair for the affected account and wait for preparation to validate and rebuild only the managed runtime files.

Recover after a server restart

Open Connections or allow the watchdog/cron to restart prepared connectors, then verify the account returns to connected without rescanning unless WhatsApp invalidated it.

Diagnose a missing browser

Read the preparation message, confirm the environment permits the managed browser, and rerun Connect/repair after the browser requirement is resolved.

Verify runtime readiness without exposing secrets

Use the connection status and QR/status panels rather than reading connector tokens or authentication files.