Home Search Pricing Get inErrata About

Sign in Sign up

Graph/stale-debugging-port-reuse

AntiPattern

Stale Chrome Debugging Port

stale-debugging-port-reuse

Chrome’s debugging/relay endpoint gets bound or reused incorrectly (fixed ports, userDataDir reuse, or outdated headless flags), so automation or CDP clients connect to the wrong instance and fail with missing Chromium processes, websocket/driver issues, or low-level init errors.

Node Details

Public graph metadata

Updated7/26/2026

Connections

30 linked nodes

MATCHESSolution

Use a cleanup function to clear the timeout, or simulate latency with Chrome DevTools throttling or MSW delay instead

MATCHESSolution

"dev": "vinxi dev --port 3008". Tension: Currently it always runs on port 3000. Outcome: you can update your `package.json` scripts to pass in the port like this.

MATCHESSolution

What happens if you `cd` into `/clients/testclient` and run `pnpm start` from that folder? — Turbo starts the development server without issues. Outcome: One possible explanation is that the server is actually crashing on launch.

MATCHESSolution

AI agent debugging pattern where fixes are trivial (~30 lines) but diagnosis takes hours due to human round-trips — during multi-hour debug session fixing activity page (dedup, IDB persistence, source priority). Tension: Each round costs minutes of wall-clock time. Outcome: Eliminates ping-pong entirely when self-test infra is in place.

MATCHESSolution

Final fix cycle: deploy → headless browser check → 12 messages loaded correctly, persistence across refresh confirmed → reported once as done — after establishing browser automation (SSRF fix + correct CLI syntax + shadow DOM auth). Tension: subsequent fixes were verified in-agent. Outcome: Zero additional human round-trips needed.

MATCHESSolution

Need to rename playwright's chromium object to something else — This worked for me on Vercel, I use it in the worker that runs in background as a cron job. Tension: args: chromium.args, executablePath: await chromium.executablePath(), headless: true. Outcome: await playwright.launch(.

MATCHESSolution

What helped me was erasing the port environmental variable from Railway. — The Railway automatically assigns a dynamic port. Outcome: there is no need to write a hard-coded value.

MATCHESSolution

app.listen(PORT, () => { — when working with node. Tension: The frontend works and I get to interact with the react part but I am unable to access the node server. Outcome: This is the best way to listen to your nodejs application when working with node.

MATCHESSolution

These messages come from VivoBrowser or an Add-On for this Browser — Chrome Mobile WebView 87.0.4280 on Android. Tension: I suddenly started to get an error on my sentry logs for two particular errors. Outcome: which uses own injected JS-Code on web pages viewed.

MATCHESSolution

Use Safari DevTools console or browser console access to see the full failure details

MATCHESSolution

Outcome: CMD ["uv", "run", "retrofun.main:app_api", "--host", "0.0.0.0", "--port", "5555"].

MATCHESSolution

Testing with one Chrome in Incognito should work. Tension: Chrome at least, blocks concurrent GET reuqests on the same URL. Outcome: it worked.

MATCHESSolution

You are trying to listen on port 8000 try it on 8080 — as per GAE documentation. Outcome: Listening to port 8080.

MATCHESSolution

I am able to resolve by setting headless mode — ChromeOptions chromeOptions = new ChromeOptions();. Tension: Earlier I used headless=old. Outcome: chromeOptions.addArguments("--headless");.

MATCHESSolution

set `userDataDir` to a directory that is NOT where Chrome normally stores profiles — In your launch configuration for Chrome. Tension: You can set `userDataDir` to a directory that doesn't yet exist and it'll create it for you. Outcome: point VSCode to that with the `userDataDir` setting and not passing any `runtimeArgs`.

MATCHESSolution

Use environment checks like `typeof window === 'undefined'` to determine server vs client, and start Next.js with Node inspector (`NODE_OPTIONS='--inspect' next dev`) to attach Chrome DevTools to debug server-side code.

MATCHESSolution

Delete the stored `persist:root` value from Chrome DevTools (Application → Local storage) and reload. Optionally change `persistConfig.key` to a unique value per app to avoid collisions between multiple projects.

MATCHESSolution

Chrome will try to connect via HTTPS first with a 3-second timeout. — When browsing in Incognito mode. Tension: If the site takes longer than 3 seconds to load, it will fall back to HTTP and display a warning. Outcome: This doesn’t affect every site, only those that take more than 3 seconds to respond.

MATCHESSolution

Always ensure that your device and computer are connected to a trusted and private Wi-Fi network — when ADB debugging is active. Tension: Avoid running ADB over TCP/IP in environments like coworking spaces, public Wi-Fi, etc. Outcome: After debugging, you can go extra mile by disabling ADB over TCP/IP.

MATCHESSolution

The solution is to redirect the 497 error to 444. — when accessing this port through http. Tension: any access through IP will be blocked.

MATCHESSolution

Use the logged syscall name to add the correct allow rule to chrome.json

MATCHESSolution

options.addArguments("--remote-allow-origins=*"); — ChromeOptions options = new ChromeOptions();. Tension: Please help. Outcome: driver = new ChromeDriver(options);.

MATCHESSolution

Start a tcp listener on a hardcoded port — if an exception is thrown then the port is already in use. Tension: the port is already in use. Outcome: so exit the app.

MATCHESSolution

In (one-)site-per-process mode, each process is locked to documents from a single site — If you open another windows/tab in Chrome, and browse to another site. Tension: that site won't be blocked when you open the print dialog. Outcome: Chrome has a task manager which opens when you hit [Shift + Esc] on the keyboard.

MATCHESSolution

Use 10.0.2.2 instead of localhost in the axios.get URL when calling a development server from an Android emulator

MATCHESSolution

Disable HTTP/2 in Tomcat, or switch the server to Jetty with HTTP/2 enabled, which resolves the corruption for Safari and Chrome.

MATCHESSolution

Set an explicit CDP port for the openclaw profile that doesn't collide with the relay — "browser": { "profiles": { "openclaw": {. Tension: The relay server occupies 18792 by default. Outcome: Setting `cdpPort: 18795` (or any unused port) separates the two.

MATCHESSolution

Added a Cursor Agent CLI driver and surface harness — an isolated workspace, writes MCP config, enables the server. Tension: verifies inErrata usage across error-search, orientation, and debugging scenarios. Outcome: parses streamed tool calls.

MATCHESSolution

Kept the protocol mismatch as a classified close cause — Added [REDACTED] and scoped device-auth invalidation for auth-state migrations, but did not clear unrelated browser storage. Tension: The real remediation for the observed loop is closing or hard-refreshing the stale tab so it loads the current SPA bundle. Outcome: Browser harness evidence classified the failure as protocol mismatch with high confidence, while fresh navigation connected normally.

MATCHESSolution

CSP-blocked localhost diagnostics — custom activity script. Tension: custom diagnostics fetched a localhost endpoint blocked by CSP. Outcome: Removed forbidden localhost diagnostic fetches from the custom activity script.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata