Startup logs
On startup, WaGo logs the runtime flags and server address:| Field | Meaning |
|---|---|
address | Interface the API binds to. Default is 0.0.0.0. |
wadebug | WhatsApp client debug level. Empty by default. |
webhookfiles | Whether inbound media files are downloaded and forwarded to webhooks. |
connectstartup | Whether WaGo reconnects sessions marked connected when the binary starts. |
storehistory | Whether history sync data is written to disk. |
Runtime flags
Common flags:| Flag | Default | Use |
|---|---|---|
-address | 0.0.0.0 | API bind address. |
-admintoken | qwert | Admin token for session/admin endpoints. Change this in production. |
-wadebug | empty | Enables WhatsApp client debug logging. Common values are INFO or DEBUG. |
-webhookfiles | true | Download inbound media and send it as webhook file upload. |
-connectstartup | true | Reconnect sessions that were connected before restart. |
-storehistory | false | Store history sync payloads under history/user_<id>/. |
-storemessage | false | Store message delivery/read status rows for /message/status. |
-retrymessage | false | Retry decrypting failed inbound messages. |
Request logs
API requests are logged with method, URL, status, response size, duration, and user ID:- Did WaGo receive the request?
- Which endpoint was called?
- Did the endpoint return 200, 400, 401, 404, or 500?
- Which WaGo user/session handled it?
- Was the request slow?
Session logs
Common session messages:| Log message | Meaning |
|---|---|
Starting websocket connection to Whatsapp | WaGo is creating the underlying WhatsApp connection for a token. |
No jid found. Creating new device | This token has no saved WhatsApp JID yet, so QR or pair-code login is needed. |
QR pair success | The phone scanned the QR or pairing completed. |
Already logged in, just connect | Saved session credentials exist and WaGo is reconnecting. |
Received kill signal | Session is being disconnected or logged out by WaGo. |
Webhook logs
Common webhook messages:| Log message | Meaning |
|---|---|
Calling webhook | WaGo found a configured webhook URL for this token. |
Skipping webhook. Not subscribed for this type | The event happened, but the token’s Subscribe list does not include that event type and is not All. |
No webhook set for user | The token has no webhook URL configured. |
Sending POST | WaGo is posting form data to the webhook URL. |
Failed to send POST request | File webhook delivery failed. Check receiver URL, TLS, timeout, or upload limits. |
Message logs
Common message logs:| Log message | Meaning |
|---|---|
Message sent | WaGo sent an outbound message and has an ID. |
Message Received | WhatsApp delivered a message event to WaGo. |
Failed to download image/audio/document/video/sticker | WaGo could not download inbound media for webhook file forwarding. |
Message was read | A read receipt arrived. |
Message delivered | A delivery receipt arrived. |
Call logs
Common call logs:| Log message | Meaning |
|---|---|
Got call offer | Incoming call offer event from WhatsApp. |
Got call accept | Remote side accepted a call. |
Got call terminate | Call ended or was terminated. |
Started browser audio receiver | WebRTC live audio began receiving browser audio. |
Failed to decode browser Opus packet | Browser sent a packet WaGo could not decode. If audio works, occasional short/empty packet logs can be harmless. |
What to collect for support
When asking for help, include:- WaGo version shown by your binary or release.
- The endpoint called.
- HTTP status and response body.
- Relevant log lines around the request.
- Whether the token is connected and logged in.
- Whether the issue happens for all contacts or one contact.
- For media, the media type and approximate file size.
- For calls, whether the browser is HTTPS and whether the network may need TURN.