2 hours ago
Hello,
I'm currently deploying a Node.js backend on Railway using whatsapp-web.js.
The deployment is successful, and the WhatsApp client initializes correctly:
- QR code is generated successfully.
- Authentication is successful.
- The "ready" event is triggered.
- The client stays connected.
However, I cannot send messages using client.sendMessage(). The request either fails or hangs, while everything else appears to be working normally.
The same code works correctly in my local environment. The issue only occurs after deploying to Railway.
Could you please let me know:
- Does Railway officially support applications using whatsapp-web.js and Puppeteer/Chromium?
- Are there any known restrictions or limitations that could prevent sendMessage() from working?
- Are there any required configurations (persistent volumes, Chromium dependencies, runtime settings, etc.) that I should enable?
I'd appreciate any guidance you can provide.
Thank you!
3 Replies
2 hours ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 2 hours ago
2 hours ago
So does that mean Railway itself restricts or blocks self-bot applications, rather than there being an issue with my code? The same code works fine locally.
2 hours ago
Self-botting is against Whatsapp's ToS, which violates Railway's AUP, so we will not provide support for it.