chrome://inspect Not Identifying Remote Target, But devtoolsFrontendUrl Works:

I’m having trouble getting Chrome’s chrome://inspect page to recognize a remote target for a Node.js debugger. Here’s the situation:

Node.js Debugger Setup:

I’m running a Node.js application with the debugger enabled on port 9229. My setup includes Docker, and the relevant part of the docker-compose.yaml is configured as follows:

abc-server:
  container_name: abc-server
  restart: on-failure
  build:
    context: ./
    dockerfile: node-server/Dockerfile
  command: sh -c "node --inspect=0.0.0.0:9229 server.js"
  ports:
    - "9229:9229"

Issue:

Despite this, the chrome://inspect page does not list the remote target. I’ve verified that localhost:9229 is correctly added under the Configure… settings in Chrome.

Workaround:

When I directly navigate to the devtoolsFrontendUrl provided in the curl response, the DevTools opens and works as expected.

Steps I’ve Tried:

1. Clearing Chrome’s cache.
2. Disabling all extensions and using incognito mode.
3. Ensuring no firewall or security software is blocking the connection.
4. Verifying that localhost:9229 is correctly configured in Chrome’s Configure... settings.