[GH-ISSUE #161] Connecting whatsapp #44

Closed
opened 2026-02-27 04:58:52 +03:00 by kerem · 19 comments
Owner

Originally created by @emrahengin on GitHub (May 15, 2024).
Original GitHub issue: https://github.com/guyzyl/whatsapp-contact-sync/issues/161

image

Originally created by @emrahengin on GitHub (May 15, 2024). Original GitHub issue: https://github.com/guyzyl/whatsapp-contact-sync/issues/161 ![image](https://github.com/guyzyl/whatsapp-contact-sync/assets/169889097/cda1199f-3887-4827-a7c6-879a1f9db809)
kerem closed this issue 2026-02-27 04:58:52 +03:00
Author
Owner

@guyzyl commented on GitHub (May 15, 2024):

Did this happen on whasync.com or when running the project locally?

<!-- gh-comment-id:2113592439 --> @guyzyl commented on GitHub (May 15, 2024): Did this happen on whasync.com or when running the project locally?
Author
Owner

@233mhz commented on GitHub (May 16, 2024):

Same issue
Captura

<!-- gh-comment-id:2114186872 --> @233mhz commented on GitHub (May 16, 2024): Same issue ![Captura](https://github.com/guyzyl/whatsapp-contact-sync/assets/18459218/69d81e23-a303-4eec-a300-e63bc6567999)
Author
Owner

@emrahengin commented on GitHub (May 16, 2024):

it happened on whasync.com

<!-- gh-comment-id:2114561428 --> @emrahengin commented on GitHub (May 16, 2024): it happened on whasync.com
Author
Owner

@guyzyl commented on GitHub (May 17, 2024):

When it didn't load, for how long did you wait?
Also, did you try refreshing the page?
(The QR can take ~15 seconds to load in some cases)

Can you please try to load it again, and if it doesn't work note down the time (and timezone) of when the issue occurred? That way I can try to find the issue in your specific session.

<!-- gh-comment-id:2117239356 --> @guyzyl commented on GitHub (May 17, 2024): When it didn't load, for how long did you wait? Also, did you try refreshing the page? (The QR can take ~15 seconds to load in some cases) Can you please try to load it again, and if it doesn't work note down the time (and timezone) of when the issue occurred? That way I can try to find the issue in your specific session.
Author
Owner

@Borkjev commented on GitHub (May 17, 2024):

Same issue here

The selfhosted docker image crashes soon after the 'authorizing' hang.

I then bought you a coffee and tried in your hosted version.
I tried around 14:51 (UTC+2)

<!-- gh-comment-id:2117545939 --> @Borkjev commented on GitHub (May 17, 2024): Same issue here The selfhosted docker image crashes soon after the 'authorizing' hang. I then bought you a coffee and tried in your hosted version. I tried around 14:51 (UTC+2)
Author
Owner

@guyzyl commented on GitHub (May 17, 2024):

Ok, I'll check it out during the weekend.

<!-- gh-comment-id:2117651041 --> @guyzyl commented on GitHub (May 17, 2024): Ok, I'll check it out during the weekend.
Author
Owner

@seemebreakthis commented on GitHub (May 18, 2024):

A little different here. Hosting locally, I am getting this. No QR code is displayed.

image

It used to work last time I tried, maybe 3 month ago. I have re-cloned and re-build but still like this.

<!-- gh-comment-id:2118673138 --> @seemebreakthis commented on GitHub (May 18, 2024): A little different here. Hosting locally, I am getting this. No QR code is displayed. ![image](https://github.com/guyzyl/whatsapp-contact-sync/assets/5940900/d7becc9a-aff8-4667-b58e-cfc606c86954) It used to work last time I tried, maybe 3 month ago. I have re-cloned and re-build but still like this.
Author
Owner

@guyzyl commented on GitHub (May 18, 2024):

I just tried loading the QR by myself (both on whasync.com and locally), both of them worked without any issue.

I did go a bit into bugs I saw in the backend server, it seems that some things have changed with WhatsApp web API causing it not to work all of the time.
In any case, I merged the changes and they should be up in whasync.com within 15 minutes.

Can one of you confirm the change fixed the issue for you?
If #162 didn't fix it, there's also this approach I can try out.

<!-- gh-comment-id:2118849992 --> @guyzyl commented on GitHub (May 18, 2024): I just tried loading the QR by myself (both on whasync.com and locally), both of them worked without any issue. I did go a bit into bugs I saw in the backend server, it seems that some things have changed with WhatsApp web API causing it not to work all of the time. In any case, I merged the changes and they should be up in [whasync.com](whasync.com) within 15 minutes. Can one of you confirm the change fixed the issue for you? If #162 didn't fix it, there's also [this approach](https://github.com/pedroslopez/whatsapp-web.js/pull/2816) I can try out.
Author
Owner

@Borkjev commented on GitHub (May 19, 2024):

The loading of the QR works just fine.

But it's hanging on WhatsApp Authorizing for over 2 minutes again.
Tested now at 09:04 (UTC+2)

<!-- gh-comment-id:2119128566 --> @Borkjev commented on GitHub (May 19, 2024): The loading of the QR works just fine. But it's hanging on WhatsApp Authorizing for over 2 minutes again. Tested now at 09:04 (UTC+2)
Author
Owner

@guyzyl commented on GitHub (May 19, 2024):

@Borkjev I was able to find the logs + replicate the issue.
The error logs I'm seeing are the same ones as yesterday, apparently #162 didn't do the trick.
I'll work on a different fix.

<!-- gh-comment-id:2119303044 --> @guyzyl commented on GitHub (May 19, 2024): @Borkjev I was able to find the logs + replicate the issue. The error logs I'm seeing are the same ones as yesterday, apparently #162 didn't do the trick. I'll work on a different fix.
Author
Owner

@guyzyl commented on GitHub (May 19, 2024):

Alright, just merged #164 which fixed the issue locally for me.
Can someone confirm it's not only me? (should be up in whasync.com in < 15 mins)

<!-- gh-comment-id:2119305578 --> @guyzyl commented on GitHub (May 19, 2024): Alright, just merged #164 which fixed the issue locally for me. Can someone confirm it's not only me? (should be up in [whasync.com](whasync.com) in < 15 mins)
Author
Owner

@seemebreakthis commented on GitHub (May 21, 2024):

Can confirm it is working for me. Hosting locally.

<!-- gh-comment-id:2121789395 --> @seemebreakthis commented on GitHub (May 21, 2024): Can confirm it is working for me. Hosting locally.
Author
Owner

@Borkjev commented on GitHub (May 21, 2024):

Seems to work on whasync.com too.

<!-- gh-comment-id:2121878947 --> @Borkjev commented on GitHub (May 21, 2024): Seems to work on whasync.com too.
Author
Owner

@guyzyl commented on GitHub (May 21, 2024):

Awesome, glad to hear

<!-- gh-comment-id:2121958109 --> @guyzyl commented on GitHub (May 21, 2024): Awesome, glad to hear
Author
Owner

@233mhz commented on GitHub (May 22, 2024):

Alright, just merged #164 which fixed the issue locally for me. Can someone confirm it's not only me? (should be up in whasync.com in < 15 mins)

14:02h (UTC +1 - From Spain)

I link the device with the QR but it does not continue.
It does not appear as an active session

<!-- gh-comment-id:2124638574 --> @233mhz commented on GitHub (May 22, 2024): > Alright, just merged #164 which fixed the issue locally for me. Can someone confirm it's not only me? (should be up in [whasync.com](whasync.com) in < 15 mins) 14:02h (UTC +1 - From Spain) I link the device with the QR but it does not continue. It does not appear as an active session
Author
Owner

@emrahengin commented on GitHub (May 22, 2024):

Solved for me (on web)

<!-- gh-comment-id:2124654535 --> @emrahengin commented on GitHub (May 22, 2024): Solved for me (on web)
Author
Owner

@guyzyl commented on GitHub (May 22, 2024):

Alright, just merged #164 which fixed the issue locally for me. Can someone confirm it's not only me? (should be up in whasync.com in < 15 mins)

14:02h (UTC +1 - From Spain)

I link the device with the QR but it does not continue. It does not appear as an active session

I checked the backend, there are no errors at all + tested it myself and it seems to be working.
For how long did you wait after scanning? Because it can take some time.

<!-- gh-comment-id:2124711745 --> @guyzyl commented on GitHub (May 22, 2024): > > Alright, just merged #164 which fixed the issue locally for me. Can someone confirm it's not only me? (should be up in [whasync.com](whasync.com) in < 15 mins) > > 14:02h (UTC +1 - From Spain) > > I link the device with the QR but it does not continue. It does not appear as an active session I checked the backend, there are no errors at all + tested it myself and it seems to be working. For how long did you wait after scanning? Because it can take some time.
Author
Owner

@233mhz commented on GitHub (May 22, 2024):

Alright, just merged #164 which fixed the issue locally for me. Can someone confirm it's not only me? (should be up in whasync.com in < 15 mins)

14:02h (UTC +1 - From Spain)
I link the device with the QR but it does not continue. It does not appear as an active session

I checked the backend, there are no errors at all + tested it myself and it seems to be working. For how long did you wait after scanning? Because it can take some time.

More than 25 min

<!-- gh-comment-id:2125209515 --> @233mhz commented on GitHub (May 22, 2024): > > > Alright, just merged #164 which fixed the issue locally for me. Can someone confirm it's not only me? (should be up in [whasync.com](whasync.com) in < 15 mins) > > > > > > 14:02h (UTC +1 - From Spain) > > I link the device with the QR but it does not continue. It does not appear as an active session > > I checked the backend, there are no errors at all + tested it myself and it seems to be working. For how long did you wait after scanning? Because it can take some time. More than 25 min
Author
Owner

@guyzyl commented on GitHub (May 24, 2024):

There were no errors at all in the past 24 hours (when I checked)

<!-- gh-comment-id:2128662988 --> @guyzyl commented on GitHub (May 24, 2024): There were no errors at all in the past 24 hours (when I checked)
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#44
No description provided.