WhatsApp pairing always returns "Try again later" after scanning QR (Evolution API 2.3.2 / Baileys 6.7.21)
维护者通常 8 天内回复
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
- Issue 类型
- 缺陷
- 描述清晰度
- 需要澄清
- 活跃度
- 冷清
- 技术栈
- docker, postgresql, redis, typescript
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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.
- 主要语言
- TypeScript
- 星标
- 9.8k
- 派生
- 7.3k
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
evolution-foundation/evolution-api 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
evolution-foundation/evolution-api#2723 ·
维护者通常 8 天内回复
-
难度 1/5 1-3 小时 新手友好度 88/100
evolution-foundation/evolution-api#2704 ·
维护者通常 8 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 68/100
evolution-foundation/evolution-api#2702 · 1 条评论 · 2 个 reaction ·
维护者通常 8 天内回复
-
[BUG] Cloud API: a single unknown wamid in a `statuses` batch silently drops the whole batch (`return` instead of `continue`)可能已有人在做 @vin1i 于 42 天前认领。 未关闭
难度 1/5 1 小时以内 新手友好度 88/100
evolution-foundation/evolution-api#2700 · 1 条评论 ·
维护者通常 8 天内回复
-
[BUG] Chatwoot integration duplicates messages when a device re-delivers the same key.id — getExistingSourceIds exists but is never called on the live path可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 76/100
evolution-foundation/evolution-api#2675 ·
维护者通常 8 天内回复
查看 evolution-foundation/evolution-api 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:other issue-rating: 🦞 diamond lobster no-stale P2
难度 2/5 1-3 小时 新手友好度 72/100
openclaw/openclaw#168089 · 2 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
✨ enhancement needs-discussion
难度 1/5 1 小时以内 新手友好度 85/100
-
[Bug]: [MCP/CLI] Bare loopback IP addresses (127.0.0.1:port) and hosts with ports fail to navigate due to erroneous scheme inference可能已有人在做 @alok-108 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
microsoft/playwright#43263 ·
维护者通常 1 天内回复
-
area:studio type:security
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复