Free, Open Source, Self-Hosted WhatsApp API Gateway
TypeScript apibotgatewayself-hostedwhatsappwhatsapp-apiwhatsapp-automationwhatsapp-botwhatsapp-gatewaywhatsapp-gateway-apiwhatsapp-webwhatsapp-web-api
docs(faq): rewrap the proxy egress paragraph
Yudhi Armyndharisc19631bb85eb
diff --git a/docs/12-troubleshooting-faq.md b/docs/12-troubleshooting-faq.mdindex ee72e00ee..18725c2aa 100644--- a/docs/12-troubleshooting-faq.md+++ b/docs/12-troubleshooting-faq.md@@ -248,8 +248,8 @@ docker compose restart openwa-apiProxy egress (if WhatsApp is blocked on your network) is configured **per session** via the`proxyUrl` field on `POST /api/sessions` or with `PATCH /api/sessions/:sessionId/proxy`, both of-which need an ADMIN key — it is **not** an environment variable, and an unreachable proxy silently blocks the WhatsApp WebSocket (see the _No QR code appears, or `/start`-returns `504`_ entry below).+which need an ADMIN key. It is **not** an environment variable, and an unreachable proxy silently+blocks the WhatsApp WebSocket (see the _No QR code appears, or `/start` returns `504`_ entry below).### Issue: Linking asks for a passkey and never completes (both engines)@@ -314,7 +314,7 @@ curl -X POST "$BASE/api/sessions/{sessionId}/start" -H "X-API-Key: $API_KEY"> ℹ️ Proxy egress for the `whatsapp-web.js` engine is configured **per session** via the> `proxyUrl` field on `POST /api/sessions` or `PATCH /api/sessions/:sessionId/proxy` (ADMIN key for-> both) — not via environment variables.+> both), not via environment variables.> ℹ️ A `504` whose body starts with `Engine initialization timed out after ...` is a **different**> failure with a different fix: initialization never finished at all. That happens when WhatsApp Web,