Closed SerpentSociety closed 5 months ago
Hello @SerpentSociety
Please checkout my comment on #3021
Hi, I am using an AWS server located in Oregon. Can this be a reason for the whatsapp qr code issue?
Hello @gunika1321 I choose that VPS which is near my location (probably same region) so Its do not send an error I have another vps which location Germany, I'm from india same server configuration and same code but does not works their.
I have also tried in Indian server and I'm also in India, but not working. I am using Debian 12 OS
hello @prashant1879, I tried shifting my server to India but it is still not working
Is there an existing issue for this?
Describe the bug
When a QR code is generated, the console logs a normal valid QR code string (example:
QR RECEIVED 2@YZ3JcY2m7irzr9qy5bnOmAbFPRCTY1um6KnoLkZeCKCPSUC1XciOdE8aBL7+76BDip2SpwvPWvrjvg==,cbuKc8eWUeBL1FFEsEx1nN0txR/HayeOOotSE10dMEA=,Rm5+jRVvLnapiWQ4euReLHnI/eBU+T+jek5vKbwuFW0=,FPtkOitGptEPPnKUHF2XRw3K3GSXFKDfHFrajlQJ13I=,1
) But, after scanning the QR code corresponding to this string, a new QR is generated, in between scanning/ authentication process by whats app, and the QR string has an undefined part (exampleQR RECEIVED undefined,cbuKc8eWUeBL1FFEsEx1nN0txR/HayeOOotSE10dMEA=,Rm5+jRVvLnapiWQ4euReLHnI/eBU+T+jek5vKbwuFW0=,FPtkOitGptEPPnKUHF2XRw3K3GSXFKDfHFrajlQJ13I=,1
), thus the authentication fails/ timeouts Any further attempt to scan using WhatsApp returns a "couldn't link device" error by WhatsAppNote: The same piece of code used to work for several months, any possibly similar issues was solved by removing the wwebjs_auth directory and reinstalling the node_modules
Expected behavior
After the QR code is generated and scanned, the device must be connected and the authentication flow shouldn't be interrupted by the generation of an undefined QR string
Steps to Reproduce the Bug or Issue
Relevant Code
Browser Type
Chromium
WhatsApp Account Type
Standard
Does your WhatsApp account have multidevice enabled?
Yes, I am using Multi Device
Environment
Additional context
No response