-
Notifications
You must be signed in to change notification settings - Fork 44
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
[BUG] Failed to connect to browser #315
Comments
FYI A quick fix for this is to open Chrome in debugging mode as well. Chrome Launch from Terminal
Bot Config
|
Same error for me too. The suggested QuickFix has no success either. |
Duplicate of #294 |
I have the same problem was anyone able to solve it? "FYI A quick fix for this is to open Chrome in debugging mode as well. Chrome Launch from Terminal open -a "Google Chrome" --args --remote-debugging-port=9222 arguments: ["-no-sandbox", "--remote-debugging-port=9222"]" did not work for me or maybe I just did not completely understand what to do :D |
Same for me. Not working and the same error message. Also the quickfix does not work |
✔️ Expected Behaviour
Connecting to Chrome works on OSX
🐞 Actual Behaviour
📋 Steps to Reproduce
PDM or executable version, not running the app as root at all - so this should be t he problem.
📺 What browsers are you seeing the problem on? (if applicable)
Chrome
💻 What operating systems are you seeing the problem on? (if applicable)
MacOS
📃 Relevant log output (if applicable)
Code of Conduct
The text was updated successfully, but these errors were encountered: