-
Notifications
You must be signed in to change notification settings - Fork 311
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
the port debug is not working #272
Comments
Doing what? Show me the command or the code that you're using. |
const client = await CDP({
// port: port,
target: `ws://localhost:${port}/devtools/browser`
}); The port is the port I am using, why do is it . Sorry, so now the port in CDP is required, before it was working. |
So now I have to use the |
The port is not required, it just defaults to 9222.
Does this give you a clue? |
yeah, i use both since they are the same otherwise its not working, thanks. |
Ciao!
How are you?
| chrome-remote-interface | latest in npm
Is Chrome running in a container? YES / NO
I execute Chrome, like this:
/opt/google/chrome/chrome --remote-debugging-port=32231 --headless --disable-gpu --enable-logging --log-level=0 --user-data-dir=/var/p3x/server.patrikx3.com/cache/chrome --user-agent="corifeus-server-renderer" about:blank
But I get this error:
I did not change anything, but now suddenly (I automatic update with npm-check-updates so it is possible I updated this npm). I get this error. Why is it trying to looking for
9222
when I specified the port and I can telnet in with the port as well.Do you have an idea why it is happening?
Patrik
The text was updated successfully, but these errors were encountered: