You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I launched fb-messenger-cli but I got the following error after giving the login credentials:
Xelp:/# fb-messenger-cli Login verification failed: No saved profile, please login Facebook credentials: Email: <mymail>@gmail.com Password: ******************************** Attempting login... Fetching login cookie Error while logging in TimeoutError: Timed out after 30000 ms while trying to connect to Chrome! The only Chrome revision guaranteed to work is r641577 Login verification failed: TimeoutError: Timed out after 30000 ms while trying to connect to Chrome! The only Chrome revision guaranteed to work is r641577 Exiting. Please try again.
Has anyone meet the same issue, and maybe solved it?
I'm running with the following:
nodejs --version
v8.16.0
The text was updated successfully, but these errors were encountered:
Looks like puppeteer can't communicate with chromium. Have you tried some of the solutions in other threads? For starters you can try various combination of sudo/admin and install paths depending on which OS you're running.
Hi,
I launched fb-messenger-cli but I got the following error after giving the login credentials:
Xelp:/# fb-messenger-cli Login verification failed: No saved profile, please login Facebook credentials: Email: <mymail>@gmail.com Password: ******************************** Attempting login... Fetching login cookie Error while logging in TimeoutError: Timed out after 30000 ms while trying to connect to Chrome! The only Chrome revision guaranteed to work is r641577 Login verification failed: TimeoutError: Timed out after 30000 ms while trying to connect to Chrome! The only Chrome revision guaranteed to work is r641577 Exiting. Please try again.
Has anyone meet the same issue, and maybe solved it?
I'm running with the following:
nodejs --version
v8.16.0
The text was updated successfully, but these errors were encountered: