-
Notifications
You must be signed in to change notification settings - Fork 203
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
how do i resolve this? #59
Comments
Did you figure out an answer to this? I am hitting the same problem. I’m self-hosting n8n in Docker ( the n8n community version 1.82.3 and have registered it) - using this docker image I’m using the MCP node at version 0.1.13 and I’m trying to use MCP-Playwright at version 0.2.10 (would you be able to rename this issue to - problems with headed browser usage) |
I figured out that I was trying to run n8n in a Docker image, which does work -- but if I want my demo to work then we need a headed browser -- so I'm switching to running n8n via npx |
@harishreddy69 when you Credential the Playwright MCP send It was at that point that I decided I needed to run First I switched to Node22 & then I installed the playwright and puppeteer-core at the root of the repo Now the Playwright is working from this [below] workflow, but it's not re-using the first window -- I'll work on that in another issue.
|
You can run the browser in Thanks, |
The text was updated successfully, but these errors were encountered: