microsoft / microsoft/playwright-dotnet

[Bug]: about: net::ERR_CONNECTION_REFUSED at https://localhost:7119/

Open
#3,311 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
3k
Forks
304
Avg merge
20h 47m
Merged PRs (30d)
6

Description

Version

1.57.0

Steps to reproduce

Example steps (replace with your own):

  1. Clone my repo at https://github.com/simix-alessandrokantousian/TestWithPlaywright
  2. run tests
  3. You should see the error: net::ERR_CONNECTION_REFUSED at https://localhost:7119/
Expected behavior

Context

  • Playwright Version: 1.57.0
  • Operating System: Windows 11
  • .NET 10
  • Browser: Chromium, Firefox

Description

I'd like to understand why I get this error when I try to run Playwright, but when I have two Visual Studio windows open—one running the project and the other running Playwright—it works. Do I need to configure something in the project to be able to run the test with only one Visual Studio window open? Or is there some configuration that makes the project run before Playwright run?

Image
Actual behavior

When I try to run Playwright happens net::ERR_CONNECTION_REFUSED at https://localhost:7119/

Additional context

No response

Environment
- Operating System: Windows 11
- CPU: AMD64 - Amd Ryzen 7000
- Browser: Chromium and Firefox
- .NET Version (TFM): [net10.0]
- Other info:

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked TestWithPlaywright repository and reproduce the failure by running its tests on Windows 11 with Playwright .NET 1.57.0. Inspect how the tested application is started and how the test run targets https://localhost:7119/. Done means the tests can start or reach the application without requiring a second Visual Studio window.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.