Pairing WhatsApp with Railway deployment - "can't link" error
Hey team, running into WhatsApp pairing issues with a Railway template deployment.
Setup:
• Deployed OpenClaw via Railway template
• Using Bright Data proxy (dedicated IP) for WhatsApp connection
• Trying to pair via WhatsApp multi-device
Issue:
When I scan the QR code, the linking process takes ages, then fails with "can't link" error. Gateway shows it's attempting to connect but the pairing never completes on the phone side.
What I've tried:
• Multiple pairing attempts
• Proxy is working (can confirm dedicated IP)
• Phone WhatsApp is up to date
Logs/config:
(Will paste relevant logs if needed — any specific ones to check?)
Anyone hit this before with Railway deployments? Is there a networking/firewall setting I'm missing, or does Railway need specific config for WebSocket persistence?
Setup:
• Deployed OpenClaw via Railway template
• Using Bright Data proxy (dedicated IP) for WhatsApp connection
• Trying to pair via WhatsApp multi-device
Issue:
When I scan the QR code, the linking process takes ages, then fails with "can't link" error. Gateway shows it's attempting to connect but the pairing never completes on the phone side.
What I've tried:
• Multiple pairing attempts
• Proxy is working (can confirm dedicated IP)
• Phone WhatsApp is up to date
Logs/config:
(Will paste relevant logs if needed — any specific ones to check?)
Anyone hit this before with Railway deployments? Is there a networking/firewall setting I'm missing, or does Railway need specific config for WebSocket persistence?
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
83,815Members
Resources
Similar Threads
Was this page helpful?
