Crushing with ERR_SOCKET_CLOSED

[Nick Loginov]

When navigating get ERR_SOCKET_CLOSED while using setProxy.

[Jared Manfredi]

Getting this as well when using page.goto and page proxies.

`node:events:353
throw er; // Unhandled 'error' event
^

Error [ERR_SOCKET_CLOSED]: Socket is closed
at new NodeError (node:internal/errors:278:15)
at Socket._writeGeneric (node:net:764:8)
at Socket._writev (node:net:781:8)
at doWrite (node:internal/streams/writable:412:12)
at clearBuffer (node:internal/streams/writable:565:5)
at Socket.Writable.uncork (node:internal/streams/writable:354:7)
at ClientRequest._flushOutput (node:_http_outgoing:934:10)
at ClientRequest._flush (node:_http_outgoing:903:22)
at node:_http_client:333:47
at callSocketMethod (node:_http_client:837:7)
Emitted 'error' event on ClientRequest instance at:
at Socket.socketErrorListener (node:_http_client:474:9)
at Socket.emit (node:events:376:20)
at emitErrorNT (node:internal/streams/destroy:188:8)
at emitErrorCloseNT (node:internal/streams/destroy:153:3)
at processTicksAndRejections (node:internal/process/task_queues:80:21) {
code: 'ERR_SOCKET_CLOSED'`