WhatsApp pairing always returns "Try again later" after scanning QR (Evolution API 2.3.2 / Baileys 6.7.21)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- docker, postgresql, redis, typescript
- Domain
- api, authentication, backend, databases, infrastructure
Research direction
Start by reproducing the QR pairing flow on the reported Evolution API, Docker, PostgreSQL, and Redis setup, then inspect the available logs around the keep-alive timeout and session establishment. Done means identifying a reproducible cause for the post-scan failure and confirming that a fresh instance reaches OPEN state.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- TypeScript
- Stars
- 9.6k
- Forks
- 7.3k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from evolution-foundation/evolution-api
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
evolution-foundation/evolution-api#2700 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
All issues in evolution-foundation/evolution-api
Similar issues
-
VerificationGate: ATTRIBUTION quote guard never matches a normal quotation (\b around the quote) Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
danielmiessler/LifeOS#2234 ·
-
T: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Mend: dependency security vulnerability untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 70/100