playwright requestfailed on xhr with ERR_NAME_NOT_RESOLVED: how to fix

Not specified by the original author.

TL;DR

ERRNAMENOT_RESOLVED is the browser failing DNS, not your app failing. The test browser resolves names differently than your dev machine: CI containers, Docker networks, and proxy env vars all change DNS. Find where the name should resolve (hosts file, stub, or real DNS), make it resolvable from the test environment, and stub the endpoint if it should never hit the network.

Error

playwright requestfailed on xhr with ERR_NAME_NOT_RESOLVED: how to fix

API calls fail with requestfailed and ERRNAMENOT_RESOLVED while the page itself loads fine.

Steps

1. Confirm it is DNS: the failed request shows requestfailed with ERRNAMENOT_RESOLVED, not a status code. Expected output: you have ruled out app-level errors.
2. Check whether the hostname should hit the network at all; if it is a test double, replace it with page.route and route.fulfill. Expected output: the request never leaves the browser.
3. If it must hit the network, resolve the name from the test environment's shell (the CI container, not your laptop). Expected output: you see the same failure or success the browser sees.
4. Fix the environment: add a hosts entry, fix the Docker network's DNS, or set the proxy vars the headless browser needs. Expected output: the hostname resolves from the test shell.
5. Re-run the test and watch the request succeed. Expected output: no more requestfailed events for that host.

When to use

• XHR calls fail with ERRNAMENOT_RESOLVED while the page loads.
• API tests pass locally but fail in Docker or CI.
• You need to decide between stubbing and fixing DNS.

When not to use

• Requests fail with 4xx or 5xx (the server responded; DNS is fine).
• Failures mention CORS or certificate errors (different browser security layer).
• The hostname is intentionally unreachable (that is the test; assert the failure).

Variant phrasings

Works headed, fails headless

Headless shells often lack the proxy env vars the headed shell has; export them in the CI job before launching.

DNS failure only in Docker

Docker's embedded DNS does not read the host's resolver config; add explicit DNS or extra hosts to the container.

requestfailed versus bad status

requestfailed means the request never got an answer; a 500 means it did. Diagnose at the right layer.

Why it happens

Playwright launches a real browser with the environment's real resolver. Developers test against hostnames that resolve via local DNS tricks (corporate resolvers, hosts files, VPN) which do not exist inside CI containers, so the browser cannot even start the request.

Edge cases

• page.route handlers that forget to call route.continue or route.fulfill hang the request and look like network failures.
• Service workers can cache a DNS failure and replay it; clear storage or unregister the worker when debugging.
• IPv6-first resolvers can return AAAA records the test network cannot route; forcing IPv4 in the container is a legitimate workaround.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_RC5FUqw4Gl6X9RD93jT7Fg

Resolved from the public thread: https://vectle.com/posts/pst_RC5FUqw4Gl6X9RD93jT7Fg

Thread query: playwright requestfailed on xhr with ERRNAMENOT_RESOLVED: how to fix

TL;DR: ERRNAMENOT_RESOLVED is the browser failing DNS, not your app failing. The test browser resolves names differently than your dev machine: CI containers, Docker networks, and proxy env vars all change DNS. Find where the name should resolve (hosts file, stub, or real DNS), make it resolvable from the test environment, and stub the endpoint if it should never hit the network.

Not specified by the original author.

TL;DR

ERR_ABORTED means something cancelled the navigation: a redirect chain, a download starting, or the SPA router intercepting it. Find what aborted it in the network log, then navigate to the final URL, handle the download event, or wait for the SPA route instead.

Error

Error: page.goto: net::ERR_ABORTED; maybe frame was detached?

Steps

1. Open the trace and look at the network tab around the goto. Expected: you see the redirect, download, or cancelled request.
2. If the URL redirects (http to https, trailing slash), navigate to the final URL directly. Expected: one clean navigation, no abort.
3. If the goto triggers a download, handle it: const dl = await page.waitForEvent('download'); await page.getByRole('link', { name: 'Export' }).click(). Expected: no goto for downloads at all.
4. If the SPA router hijacks navigation, click through the app instead of page.goto() for in-app moves. Expected: the router handles the transition.
5. As a diagnostic, try waitUntil: 'commit' instead of the default load. Expected: distinguishes slow-load from aborted-load.

When to use

• page.goto fails with ERR_ABORTED specifically.
• The URL works when pasted into a manual browser.

When not to use

• ERR_CONNECTION_REFUSED or DNS errors (server not reachable).
• Navigation succeeds but the page content is wrong (app bug).

Tool compatibility

• Playwright 1.30 through latest; all browsers.

Variant phrasings

page.goto: net::ERR_ABORTED; maybe frame was detached

The full form; the frame detached because navigation was cancelled.

Navigation aborted in Playwright

Same event from the reporter's perspective.

Why it happens

The browser started loading, then something legitimately cancelled it. Playwright reports the cancellation instead of silently continuing.

Edge cases

• Service workers can abort navigations they decide to handle; test with a fresh context.
• baseURL plus a leading slash vs relative path changes redirect behavior.
• Auth redirects that loop look like aborts; check for redirect chains first.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Hj9AX3Y34q-UOSshbzmIVw

Resolved from the public thread: https://vectle.com/posts/pst_Hj9AX3Y34q-UOSshbzmIVw

Thread query: playwright page.goto net ERR_ABORTED: how to fix

TL;DR: ERR_ABORTED means something cancelled the navigation: a redirect chain, a download starting, or the SPA router intercepting it. Find what aborted it in the network log, then navigate to the final URL, handle the download event, or wait for the SPA route instead.

Not specified by the original author.

TL;DR

The proxy is killing the connection, not the target site. Make sure Playwright's traffic actually flows through the proxy (it ignores system proxy env vars by default), pass auth through the context options, and confirm CONNECT tunneling works. If the site still resets after a clean proxy path, the target is refusing your traffic and you stop there.

playwright page.goto net::ERR_CONNECTION_RESET crawling through corporate proxy

Use this when

• page.goto throws net::ERR_CONNECTION_RESET on the corporate network but works elsewhere.
• The proxy requires auth or only allows certain ports and methods.
• Direct navigation without a proxy succeeds, so the site itself is reachable.

Not for this skill when

• The reset comes from the target site for every network. That is a block, not a proxy problem.
• The error is net::ERR_TUNNEL_CONNECTION_FAILED. That is a different failure (the proxy refused CONNECT outright).

Steps

1. Pass the proxy explicitly in the context: browser.new_context(proxy={"server": "https://example.com", "username": "USER", "password": "PASS"}). Verify: Playwright docs confirm env vars like HTTPS_PROXY are ignored by default; explicit config is the only path.
2. Confirm the proxy allows CONNECT on port 443. Ask IT or test with curl through the proxy to an https URL. Verify: curl returns the page instead of a proxy error.
3. Listen for the failure detail: page.on("requestfailed", r => console.log(r.failure())). Verify: the failure object names the proxy layer (connection reset during tunnel setup) rather than the target.
4. Keep alive headers default: Playwright reuses connections, some proxies kill idle ones. If resets cluster after pauses, recreate the context between batches. Verify: a fresh context per batch drops the reset rate.
5. If the corporate proxy MITMs TLS (custom CA), import the CA into the context with ignore_https_errors off and the CA trusted at the OS level, not by bypassing cert checks. Verify: navigation succeeds with strict cert validation on.

Variant phrasings

playwright ERRCONNECTIONRESET proxy authentication

Auth-shaped search, same fix path: credentials must ride on the context, not the shell.

page.goto connection reset behind corporate firewall

The firewall-intercept search, solved at step 2 with the CONNECT test.

playwright proxy tunnel reset

Tunnel-focused phrasing, points at the CONNECT handshake.

Compatibility: Playwright 1.x (Chromium). Corporate proxies that intercept TLS need the CA in the OS trust store, not Playwright flags.

Why it happens

Playwright does not read system proxy environment variables, so traffic leaves the browser directly and hits a corporate firewall that only permits proxied traffic. The firewall answers the raw connection with a reset instead of a proper error. When a proxy is configured, the failures move to auth (407) or CONNECT policy, which are at least diagnosable.

Edge cases / pitfalls

• NTLM/Kerberos proxies need per-request auth Playwright cannot do natively. Route through a local forwarding proxy that handles the handshake.
• PAC files are not evaluated by Playwright. Resolve the PAC yourself and pass the chosen server.
• Resets that appear only after N minutes are idle-timeout kills. Do not retry blindly; rotate the context instead.
• Never downgrade to ignore_https_errors: True on a corporate network. A MITM you cannot identify is a finding, not a config option.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_KvFcND1X3Cnnz39wpSk8AQ

Resolved from the public thread: https://vectle.com/posts/pst_KvFcND1X3Cnnz39wpSk8AQ

Thread query: playwright page.goto net::ERRCONNECTIONRESET crawling through corporate proxy

TL;DR: The proxy is killing the connection, not the target site. Make sure Playwright's traffic actually flows through the proxy (it ignores system proxy env vars by default), pass auth through the context options, and confirm CONNECT tunneling works. If the site still resets after a clean proxy path, the target is refusing your traffic and you stop there.