[Bug]: New install "Internal error: unable to connect to the test serverplaywright" about playwright

[Ksingh22]

I had the same issue. I renamed the file from Playwright.config.js to Playwright.configs.js and it worked. Not getting "Internal error: unable to connect to the test serverplaywright"

[mchequer]

those commands produce the same error. On other machines it's fine, there is something about this machine and it's setup. It's used for a lot of other development things (Visual Code, MySQL +++ ), so probably something there is affecting it. I've checked event logs, rebooted, disabled all kinds of stuff, as much as i can to see what could be the issue. I will probably just reinstall the machine and start over. Thank you for lookingBest,Mark On Wednesday, June 12, 2024 at 10:57:13 AM PDT, Yury Semikhatsky ***@***.***> wrote: Hmm, this I can't reproduce. Just to double check, are you doing exact following steps? - npm init playwright newplaywright - cd newplaywright - code . - Click on green triangle on one of the test's gutter to run it. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[Ksingh22]

I had the same issue. I renamed the file from Playwright.config.js to Playwright.configs.js and it worked. Not getting "Internal error: unable to connect to the test serverplaywright"

It works for me. But why ?

I had the same issue. I renamed the file from Playwright.config.js to Playwright.configs.js and it worked. Not getting "Internal error: unable to connect to the test serverplaywright"

This will not fix the issue, as playwright will not be able to see your config (which the correct filename is playwright.config.ts or playwright.config.js.

Just checked, the test tab will not display your tests and will ignore your config with playwright.configs.js

I have another extension of test runner installed, so that's why test tab was not missing. However you are correct, I have updated the node version and that error is not happening.
Thanks!

[yury-s]

Does it reproduce if you open VS Code in a project created via npm init playwright new_project ?

There might be some race condition during the steps you run. At step 3 do you install playwright via VSCode command or by running a command in terminal? When do you initialize npm package?

[mchequer]

Same error. When I enter "npm init playwright newplaywright" I am prompted to install create-playwright (which i did). But i still get the same error. [cid:d30be892-0435-4669-b914-ef3287fc327f]

…

________________________________ From: Yury Semikhatsky ***@***.***> Sent: Wednesday, June 12, 2024 9:06 AM To: microsoft/playwright ***@***.***> Cc: Mark Chequer ***@***.***>; Author ***@***.***> Subject: Re: [microsoft/playwright] [Bug]: New install "Internal error: unable to connect to the test serverplaywright" (Issue #31277) Does it reproduce if you open VS Code in a project created via npm init playwright new_project ? — Reply to this email directly, view it on GitHub<#31277 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQSOTCH2PEOKAR5IK6L7CTLZHBWZHAVCNFSM6AAAAABJGL7EHCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRTGQYTSMBXHE>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[yury-s]

Hmm, this I can't reproduce. Just to double check, are you doing exact following steps?

1. npm init playwright newplaywright
2. cd newplaywright
3. code .
4. Click on green triangle on one of the test's gutter to run it.

[yury-s]

Closing this report for now. Feel free to file another issue if reinstalling doesn't help or you discover something that could help us reproduce it locally.

[3cognito]

Faced the same issue today: unresolved.

[kalmigs]

Same here, new install and got this error

[eustachi0]

I have encountered this issue on my Windows 10 pc. It works fine if you are using WSL.
I have a laptop that runs Windows 11, VS Code 1.90.2 and WSL2 -> Playwright works fine.

I have a pc that runs Windows 10, VS Code 1.90.2 without WSL2, when I create a new fresh Playwright install, the playwright config file throws an error saying "unable to connect to the test server". This happens on any new projects.

[kalmigs]

Fixed my issue by using the latest node version (previously was on v20.6.0).

[kalmigs]

I had the same issue. I renamed the file from Playwright.config.js to Playwright.configs.js and it worked. Not getting "Internal error: unable to connect to the test serverplaywright"

This will not fix the issue, as playwright will not be able to see your config (which the correct filename is playwright.config.ts or playwright.config.js.

Just checked, the test tab will not display your tests and will ignore your config with playwright.configs.js

[danaoairuike]

I had the same issue. I renamed the file from Playwright.config.js to Playwright.configs.js and it worked. Not getting "Internal error: unable to connect to the test serverplaywright"

It works for me. But why ?

[raymondseahwc]

Hi, may i check which node version you are on that resolve this issue?

without having the need to rename the "playwright.config.ts" to "playwright.configs.ts"