[GH-ISSUE #225] Stuck on "Whatsapp Authorizing" #65

Open
opened 2026-02-27 04:59:00 +03:00 by kerem · 6 comments
Owner

Originally created by @IberianSoldierPC on GitHub (Sep 14, 2025).
Original GitHub issue: https://github.com/guyzyl/whatsapp-contact-sync/issues/225

Hi,

I successfully built and ran the Docker container. The web interface loads, and the WhatsApp QR code appears correctly. However, after scanning the QR code, the status stays at: WhatsApp authorizing

I’ve tried:

  • Rebuilding the Docker image from scratch
  • Clearing browser cache and cookies
  • Checking container logs — no errors related to WhatsApp initialization

Environment:

Docker version: latest
Node version in container: 21-alpine
Browser: Chrome/Firefox (latest)
OS: w11

Could you please advise what might be causing the authorization to get stuck after scanning the QR code?

Thank you!

Originally created by @IberianSoldierPC on GitHub (Sep 14, 2025). Original GitHub issue: https://github.com/guyzyl/whatsapp-contact-sync/issues/225 Hi, I successfully built and ran the Docker container. The web interface loads, and the WhatsApp QR code appears correctly. However, after scanning the QR code, the status stays at: WhatsApp authorizing I’ve tried: - Rebuilding the Docker image from scratch - Clearing browser cache and cookies - Checking container logs — no errors related to WhatsApp initialization Environment: Docker version: latest Node version in container: 21-alpine Browser: Chrome/Firefox (latest) OS: w11 Could you please advise what might be causing the authorization to get stuck after scanning the QR code? Thank you!
Author
Owner

@guyzyl commented on GitHub (Sep 18, 2025):

Is your phone getting locked in the process? It might cause WhatsApp to not authorize.

In addition to that, there are some issues that recently arose specifically around the WhatsApp API.
Unfortunately I do not have time to investigate them, so I hope you figure it out and get it to work!

<!-- gh-comment-id:3308508395 --> @guyzyl commented on GitHub (Sep 18, 2025): Is your phone getting locked in the process? It might cause WhatsApp to not authorize. In addition to that, there are some issues that recently arose specifically around the WhatsApp API. Unfortunately I do not have time to investigate them, so I hope you figure it out and get it to work!
Author
Owner

@meneses-pt commented on GitHub (Sep 19, 2025):

@guyzyl I know you said you don't have the time to investigate, but I was able to have it working by downgrading whatsapp-web.js to 1.23.0. Not sure why :/

Might be useful to others as well

<!-- gh-comment-id:3312479264 --> @meneses-pt commented on GitHub (Sep 19, 2025): @guyzyl I know you said you don't have the time to investigate, but I was able to have it working by downgrading whatsapp-web.js to 1.23.0. Not sure why :/ Might be useful to others as well
Author
Owner

@guyzyl commented on GitHub (Sep 20, 2025):

That’s good to know! Do you mind opening a PR for that? I’ll approve and
merge it :)

On Fri, Sep 19, 2025 at 18:41 André Meneses @.***>
wrote:

meneses-pt left a comment (guyzyl/whatsapp-contact-sync#225)
https://github.com/guyzyl/whatsapp-contact-sync/issues/225#issuecomment-3312479264

@guyzyl https://github.com/guyzyl I know you said you don't have the
time to investigate, but I was able to have it working by downgrading
whatsapp-web.js to 1.23.0. Not sure why :/

Might be useful to others as well


Reply to this email directly, view it on GitHub
https://github.com/guyzyl/whatsapp-contact-sync/issues/225#issuecomment-3312479264,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXAJMGCPGYSPCYJP23YDUL3TQI2DAVCNFSM6AAAAACGPVMA7OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGMJSGQ3TSMRWGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

<!-- gh-comment-id:3314614738 --> @guyzyl commented on GitHub (Sep 20, 2025): That’s good to know! Do you mind opening a PR for that? I’ll approve and merge it :) On Fri, Sep 19, 2025 at 18:41 André Meneses ***@***.***> wrote: > *meneses-pt* left a comment (guyzyl/whatsapp-contact-sync#225) > <https://github.com/guyzyl/whatsapp-contact-sync/issues/225#issuecomment-3312479264> > > @guyzyl <https://github.com/guyzyl> I know you said you don't have the > time to investigate, but I was able to have it working by downgrading > whatsapp-web.js to 1.23.0. Not sure why :/ > > Might be useful to others as well > > — > Reply to this email directly, view it on GitHub > <https://github.com/guyzyl/whatsapp-contact-sync/issues/225#issuecomment-3312479264>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAXAJMGCPGYSPCYJP23YDUL3TQI2DAVCNFSM6AAAAACGPVMA7OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGMJSGQ3TSMRWGQ> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >
Author
Owner

@meneses-pt commented on GitHub (Sep 20, 2025):

https://github.com/guyzyl/whatsapp-contact-sync/pull/227

<!-- gh-comment-id:3314829576 --> @meneses-pt commented on GitHub (Sep 20, 2025): https://github.com/guyzyl/whatsapp-contact-sync/pull/227
Author
Owner

@mattguk commented on GitHub (Sep 24, 2025):

@meneses-pt thanks very much for sharing this fix, works for me as well

<!-- gh-comment-id:3327454811 --> @mattguk commented on GitHub (Sep 24, 2025): @meneses-pt thanks very much for sharing this fix, works for me as well
Author
Owner

@MRDGH2821 commented on GitHub (Oct 5, 2025):

Updating whatsapp-web.js to v1.34.1 also helped!

<!-- gh-comment-id:3368674035 --> @MRDGH2821 commented on GitHub (Oct 5, 2025): Updating whatsapp-web.js to v1.34.1 also helped!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/whatsapp-contact-sync#65
No description provided.