Common WhatsApp Bot Hosting Errors, and Fixes

WhatsApp bots have a distinct set of failure modes compared to Telegram/Discord, mostly centered around session authentication. Here's what each one actually means.

QR Code Keeps Regenerating, Never Confirms

• Scan it promptly once it appears in the console — these codes expire after a short window.
• Make sure you're scanning with Settings → Linked Devices → Link a Device in WhatsApp, not the regular camera app.
• If it keeps failing repeatedly, restart the bot process to get a fresh code rather than scanning a stale one that's already expired.

"Session closed" / Bot Logged Out Unexpectedly

• WhatsApp occasionally force-logs-out linked sessions — this can happen after being logged in on too many linked devices, after very high message-sending volume that looks automated/spammy, or just periodically for security.
• If your session folder (.wwebjs_auth for whatsapp-web.js, or your Baileys auth folder) got deleted or corrupted, you'll need to re-scan the QR code from scratch — see our deployment guide for protecting that folder going forward.

Puppeteer / Chromium Launch Errors (whatsapp-web.js specifically)

• Usually means not enough RAM for the headless browser to actually start — see our plan guide and consider moving up a tier, especially if you're on Micro.
• Check your library version is current — Puppeteer occasionally needs updates to stay compatible with newer WhatsApp Web versions.

Messages Send But Are Delayed or Drop Under Load

• Check actual RAM/CPU usage during a busy period — both libraries (especially whatsapp-web.js) can fall behind under sustained high message volume on an undersized plan.
• If you're on whatsapp-web.js and this is a recurring problem, consider Baileys instead — see our library comparison, since its lower overhead handles volume more gracefully on the same specs.

"Rate limited" / Number Temporarily Restricted

WhatsApp actively watches for automated-looking behavior (very high send rates, sending to many new contacts quickly, identical repeated messages). This is a WhatsApp-side policy enforcement, not a hosting issue — space out sends, avoid blasting identical messages to many numbers in a short window, and treat the account like you would a real human's, not a mass-messaging tool.

Bot Process Running But Not Receiving Messages

• Confirm the WhatsApp account's phone itself still has an active internet connection — depending on the library and WhatsApp's multi-device mode, some message flows can depend on the linked phone's own connectivity, not just your server's.
• Check the console for any reconnection/error loop that might indicate the WebSocket connection dropped and isn't recovering — see our 24/7 uptime guide for adding reconnect logic.

Still Stuck?

Open a support ticket with your service ID, which library you're using, and the exact console output — that's enough for us to tell you definitively whether it's a resource issue, a library bug, or WhatsApp-side enforcement.