Environment
- Evolution API 2.3.2
- Baileys 6.7.21
- Fresh installation
- Docker
- PostgreSQL
- Redis
- Ubuntu VPS (Hostinger)
Problem
The instance is created successfully.
The QR Code is generated correctly.
The phone scans the QR Code successfully.
Immediately after scanning, WhatsApp shows:
Try again later
The instance never reaches OPEN state.
Logs
Error: Timed Out
error in sending keep alive
Tests already performed
- Fresh PostgreSQL
- Fresh Redis
- Fresh Evolution installation
- Fresh database
- Fresh Docker image
- Baileys downgraded from rc.9 to 6.7.21
- HTTPS connectivity OK
- TLS connectivity OK
- DNS OK
- IPv4 OK
- IPv6 OK
The exact same behavior occurs with both:
- Evolution 2.3.7 (Baileys rc.9)
- Evolution 2.3.2 (Baileys 6.7.21)
Could someone help identify why WhatsApp always refuses the pairing with "Try again later"?
Additional information:
This problem has persisted for several weeks.
The QR Code is valid and is read successfully by WhatsApp.
The failure occurs only after the QR is accepted by the phone.
This suggests the failure happens during the authentication/session establishment step, not during QR generation.
Environment
Problem
The instance is created successfully.
The QR Code is generated correctly.
The phone scans the QR Code successfully.
Immediately after scanning, WhatsApp shows:
The instance never reaches OPEN state.
Logs
Tests already performed
The exact same behavior occurs with both:
Could someone help identify why WhatsApp always refuses the pairing with "Try again later"?
Additional information:
This problem has persisted for several weeks.
The QR Code is valid and is read successfully by WhatsApp.
The failure occurs only after the QR is accepted by the phone.
This suggests the failure happens during the authentication/session establishment step, not during QR generation.