New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
restart authorized instance wppconnect failed #1366
Comments
if I change to old versions wppconnect, wa.js and whatsapp-web - authorized session up after reboot successful.
|
yes facing the same issue |
same |
up to latest wppconnect@1.17.1, wa.js@2.13.2, wa-version@1.1.174 |
Issue is not resolved. Same issue is persisting |
Issue still persists in 1.18.0 |
On 16 independent bots, so far no issues with 1.18.0
|
@rsaisankalp, please, make a test with 1.18.1 |
Updated to 1.18.1, reboot and no problems (so far) WhatsApp WEB version: 2.2230.15 |
after connecting in 1.18.1 restarting it doesn't authorize the session. |
I tested with wppconnect@1.18.1 and whatsapp-web 2.2240.7-beta - all good |
Thank's @antirek |
Wppconnect 1.18.1 Unable to reconnect. wppconne | info: Checking for updates 1|wppconnect | info: [919686188814:client] WhatsApp WEB version: 2.2234.13 |
Description
wppconnect instance was started, after reading qr-code, instance authorized - and i can send/receive messages.
sometimes wppconnect eat a lot of RAM, and I restarted it. But instance doesn't start. Browser show that whatsapp-web is loading and nothing. After clearing of browser directory I must again start wppconnect instance and read qr-code.
Earlier wppconnect instance start without any additional authorizations after reboot.
In logs:
start clear wppconnect instance:
after reboot
after delete token dir and start clear wppconnect instance - read qr-code again and can use to next reboot ))
Environment
The text was updated successfully, but these errors were encountered: