Skip to content
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

Closed
antirek opened this issue Oct 11, 2022 · 14 comments
Closed

restart authorized instance wppconnect failed #1366

antirek opened this issue Oct 11, 2022 · 14 comments
Assignees
Labels
bug Something isn't working needs triage

Comments

@antirek
Copy link
Contributor

antirek commented Oct 11, 2022

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:

info:     You're up to date
info:     [whatsappsession:browser] Using browser folder './tokens/whatsappsession'
info:     [whatsappsession:browser] Initializing browser...
info:     [whatsappsession:client] Initializing...
Status { statusSession: 'notLogged', session: 'whatsappsession' }
qr code callback start
info:     [whatsappsession:client] WhatsApp WEB version: 2.2236.10
info:     [whatsappsession:client] WA-JS version: 2.13.1
info:     [whatsappsession:session] Session Unpaired
Status { statusSession: 'qrReadSuccess', session: 'whatsappsession' }
Status { statusSession: 'inChat', session: 'whatsappsession' }

after reboot

info:     You're up to date
info:     [whatsappsession:browser] Using browser folder './tokens/whatsappsession'
info:     [whatsappsession:browser] Initializing browser...
info:     [whatsappsession:client] Initializing...
info:     [whatsappsession:client] WhatsApp WEB version: 2.2236.10
info:     [whatsappsession:client] WA-JS version: 2.13.1

no any data continue 5 minutes 

Screenshot from 2022-10-11 13-50-43

after delete token dir and start clear wppconnect instance - read qr-code again and can use to next reboot ))

Environment

  • WPPConnect version(s): 1.17.1
  • WA-JS version(s): 2.13.1
  • Browser: Chrome 106
  • OS: Ubuntu 20.04
  • Node version: Node 16.15.1
  • WhatsApp version: 2.2236.10
  • MultiDevice (BETA): yes
@antirek antirek added bug Something isn't working needs triage labels Oct 11, 2022
@antirek
Copy link
Contributor Author

antirek commented Oct 11, 2022

if I change to old versions wppconnect, wa.js and whatsapp-web - authorized session up after reboot successful.

  • WPPConnect version(s): 1.16.1
  • WA-JS version(s): 2.11.0
  • Browser: Chrome 106
  • OS: Ubuntu 20.04
  • Node version: Node 16.15.1
  • WhatsApp version: 2.2230.15
  • MultiDevice (BETA): yes

@rsaisankalp
Copy link

yes facing the same issue

@jesusvalverde
Copy link

same

@edgardmessias edgardmessias self-assigned this Oct 13, 2022
@dionatanfmsilva
Copy link

Same problem here
Testing on my local machine displays these errors on the console

001

@antirek
Copy link
Contributor Author

antirek commented Oct 17, 2022

up to latest wppconnect@1.17.1, wa.js@2.13.2, wa-version@1.1.174
also try test other versions wa-web:
2.2230.15 - all ok
2.2232.8 - all ok
2.2234.13 - all ok
2.2236.10 - problem
2.2238.7 - problem

@rsaisankalp
Copy link

Issue is not resolved. Same issue is persisting

@rsaisankalp
Copy link

Issue still persists in 1.18.0

@jesusvalverde
Copy link

On 16 independent bots, so far no issues with 1.18.0

  • WA-JS version: 2.13.3
  • whatsappVersion: '2.2230.15',

@edgardmessias
Copy link
Contributor

@rsaisankalp, please, make a test with 1.18.1

@jesusvalverde
Copy link

Updated to 1.18.1, reboot and no problems (so far)

WhatsApp WEB version: 2.2230.15
WA-JS version: 2.13.3

@rsaisankalp
Copy link

rsaisankalp commented Oct 20, 2022

after connecting in 1.18.1

restarting it doesn't authorize the session.
facing following error on reboot
1|wppconnect | _ ______ ____ ______ __
1|wppconnect | | | / / __ / __ / / ____ ____ ___ ____/ /
1|wppconnect | | | /| / / /
/ / // / / / __ / __ / __ / _ / / /
1|wppconnect | | |/ |/ / ___/ / // // / / / / / / / / // /
1|wppconnect | |/|
/
/ /
/ _/_// /// //_/_/__/
1|wppconnect | info: Checking for updates
1|wppconnect | info: You're up to date
1|wppconnect | info: [919686188814:browser] Using browser folder './userDataDir/919686188814'
1|wppconnect | info: [919686188814:browser] Initializing browser...
1|wppconnect | info: [919686188814:client] Initializing...
1|wppconnect | info: [919686188814:client] WhatsApp WEB version: 2.2234.13
1|wppconnect | info: [919686188814:client] WA-JS version: 2.13.3
1|wppconnect | info: [919686188814:client] Auto close configured to 60s
1|wppconnect | info: 2022-10-20T18:27:52.510Z isLogged
1|wppconnect | info: [919686188814:client] Auto close configured to 60s
1|wppconnect | info: [919686188814:client] Closing the page
1|wppconnect | info: 2022-10-20T18:28:52.778Z browserClose
1|wppconnect | error: 2022-10-20T18:28:52.856Z Protocol error (Runtime.callFunctionOn): Session closed. Most likely the page has been closed. - Error: Protocol error (Runtime.callFunctionOn): Session closed. Most likely the page has been closed.
1|wppconnect | at CDPSession.send (/home/ec2-user/whatsappserver/wppconnect-server/node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:265:35)
1|wppconnect | at ExecutionContext._ExecutionContext_evaluate (/home/ec2-user/whatsappserver/wppconnect-server/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:268:46)
1|wppconnect | at ExecutionContext.evaluate (/home/ec2-user/whatsappserver/wppconnect-server/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:117:113)
1|wppconnect | at DOMWorld.evaluate (/home/ec2-user/whatsappserver/wppconnect-server/node_modules/puppeteer/lib/cjs/puppeteer/common/DOMWorld.js:191:24)

@antirek
Copy link
Contributor Author

antirek commented Oct 21, 2022

I tested with wppconnect@1.18.1 and whatsapp-web 2.2240.7-beta - all good
@edgardmessias thanks!
@rsaisankalp up whatsapp-web version

@edgardmessias
Copy link
Contributor

Thank's @antirek

@rsaisankalp
Copy link

Wppconnect 1.18.1
WA web version 2.2234.13

Unable to reconnect.
Numbers gets disconnected within one day
Some times recovers sometimes not

wppconne | info: Checking for updates
1|wppconne | info: [919686188814:browser] Using browser folder './userDataDir/919686188814'
1|wppconne | info: [919686188814:browser] Initializing browser...
1|wppconne | info: You're up to date
1|wppconne | info: [916281503099:browser] Using browser folder './userDataDir/916281503099'
1|wppconne | info: [916281503099:browser] Initializing browser...
1|wppconne | info: [919686188814:client] Initializing...
1|wppconne | info: [916281503099:client] Initializing...

1|wppconnect | info: [919686188814:client] WhatsApp WEB version: 2.2234.13
1|wppconnect | info: [919686188814:client] WA-JS version: 2.13.3
1|wppconnect | info: [919686188814:client] Auto close configured to 60s
1|wppconnect | info: 2022-10-22T01:02:55.306Z isLogged
1|wppconnect | info: [919686188814:client] Auto close configured to 60s
1|wppconnect | info: [916281503099:client] WhatsApp WEB version: 2.2234.13
1|wppconnect | info: [916281503099:client] WA-JS version: 2.13.3
1|wppconnect | info: [916281503099:client] Auto close configured to 60s
1|wppconnect | info: 2022-10-22T01:02:56.505Z isLogged
1|wppconnect | info: [916281503099:client] Auto close configured to 60s
1|wppconnect | info: [919686188814:client] Closing the page
1|wppconnect | info: 2022-10-22T01:03:55.588Z browserClose
1|wppconnect | error: 2022-10-22T01:03:55.750Z Protocol error (Runtime.callFunctionOn): Session closed. Most likely the page has been closed. - Error: Protocol error (Runtime.callFunctionOn): Session closed. Most likely the page has been closed.
1|wppconnect | at CDPSession.send (/home/ec2-user/whatsappserver/wppconnect-server/node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:265:35)
1|wppconnect | at ExecutionContext._ExecutionContext_evaluate (/home/ec2-user/whatsappserver/wppconnect-server/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:268:46)
1|wppconnect | at ExecutionContext.evaluate (/home/ec2-user/whatsappserver/wppconnect-server/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:117:113)
1|wppconnect | at DOMWorld.evaluate (/home/ec2-user/whatsappserver/wppconnect-server/node_modules/puppeteer/lib/cjs/puppeteer/common/DOMWorld.js:191:24)
1|wppconnect | info: [916281503099:client] Closing the page
1|wppconnect | info: 2022-10-22T01:03:56.745Z browserClose
1|wppconnect | error: 2022-10-22T01:03:56.885Z Protocol error (Runtime.callFunctionOn): Session closed. Most likely the page has been closed. - Error: Protocol error (Runtime.callFunctionOn): Session closed. Most likely the page has been closed.
1|wppconnect | at CDPSession.send (/home/ec2-user/whatsappserver/wppconnect-server/node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:265:35)
1|wppconnect | at ExecutionContext._ExecutionContext_evaluate (/home/ec2-user/whatsappserver/wppconnect-server/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:268:46)
1|wppconnect | at ExecutionContext.evaluate (/home/ec2-user/whatsappserver/wppconnect-server/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:117:113)
1|wppconnect | at DOMWorld.evaluate (/home/ec2-user/whatsappserver/wppconnect-server/node_modules/puppeteer/lib/cjs/puppeteer/common/DOMWorld.js:191:24)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs triage
Projects
None yet
Development

No branches or pull requests

5 participants