🐛 BUG: Error in ProxyController: Could not connect to InspectorProxyWorker

[erictoman]

Which Cloudflare product(s) does this pertain to?

Wrangler core

What version(s) of the tool(s) are you using?

"wrangler": "^3.19.0"

What version of Node are you using?

20.9

What operating system are you using?

Manjaro

Describe the Bug

This happen to me on debian and arch based OS.
Error in ProxyController: Failed to send message to InspectorProxyWorker: {"type":"reloadStart"}
MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
at #assembleAndUpdateConfig (/home/eric/Documents/broken-shape-ce76/node_modules/miniflare/dist/src/index.js:8889:13)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Mutex.runWith (/home/eric/Documents/broken-shape-ce76/node_modules/miniflare/dist/src/index.js:3861:16) {
code: 'ERR_RUNTIME_FAILURE',
cause: undefined
}
=> Error contextual data: {
config: {
name: 'broken-shape-ce76',
script: { contents: '' },
dev: {
server: [Object],
inspector: [Object],
urlOverrides: [Object],
liveReload: false
}
},
bundle: undefined
}

Please provide a link to a minimal reproduction

No response

Please provide any relevant error logs

No response

[mattallty]

Same error here, same trace. Rolling back to 3.18.0 fixes the issue.
MacOS Sonoma 14.1, node v20.9.0

[mrbbot]

Hey! 👋 Would you be able to provide a minimal reproduction for this issue? Without that, it's unlikely we'll be able to solve this issue.

[coderovich]

faced with the same issue. Vagrant, Debian 12. NodeJS 20.10. Wrangler > 3.18.0 (3.19, 3.20, 3.21)
"Hello World" template.

When i'm trying to set up specific port:
$: wrangler dev --ip=192.168.83.140 --log-level=debug

getting

Error in ProxyController: Could not connect to InspectorProxyWorker
 SyntaxError: Unexpected end of JSON input

P.S. $: wrangler dev without --ip works properly

[lrapoport-cf]

hi @coderovich :) it looks like the error you're seeing is different than what's reported in this issue. are you still encountering this? if so, could you please file a separate issue for it so we can track it appropriately?

@erictoman can you please provide a minimal repro?

[lrapoport-cf]

hi @erictoman :) we haven't heard from you in a while, so we’re going to close this issue for now, but if this is still a problem, please feel free to open a new issue referencing this one. please be sure to include an updated summary and any additional requested details, followup, or context and we will revisit and investigate further. thanks!