Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(session): describe how each engine handles an unreachable proxy

Yudhi Armyndharis2455b8def611
diff --git a/src/modules/session/dto/session-proxy.dto.ts b/src/modules/session/dto/session-proxy.dto.ts
index 0a2b7c7e7..f4e9aae9c 100644
--- a/src/modules/session/dto/session-proxy.dto.ts
+++ b/src/modules/session/dto/session-proxy.dto.ts
@@ -55,7 +55,8 @@ export class UpdateSessionProxyDto {
description:
'Per-session egress proxy URL (http/https/socks4/socks5; credentialed form allowed). Send ' +
'`null` to clear the proxy. Must be a real, reachable proxy — an unreachable value blocks the ' +
- 'WhatsApp WebSocket and session start times out (~30s).',
+ 'WhatsApp WebSocket (no QR is delivered). On whatsapp-web.js the session start then times out ' +
+ '(~30s); on Baileys the start succeeds and the session keeps retrying the connection.',
type: String,
nullable: true,
maxLength: 255,