-
Notifications
You must be signed in to change notification settings - Fork 497
Closed
Labels
P3Low: Not priority right nowLow: Not priority right nowkind/supportA question or request for supportA question or request for supportstatus/readyReady to be workedReady to be worked
Description
Type: Question
Severity: Low
Description: When a node is disconnected from the internet, when internet comes back, it shows the below error. Obviously because it can't open a webscoket connection with another node. But my question is, can we catch it?
WebSocket connection to 'ws://127.0.0.1:8081/' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED
module.exports @ F:\classwork\madnet\node_modules\pull-ws\client.js:18
dial @ F:\classwork\madnet\node_modules\libp2p-websockets\src\index.js:26
timeout @ F:\classwork\madnet\node_modules\libp2p-switch\src\limit-dialer\queue.js:79
(anonymous) @ F:\classwork\madnet\node_modules\async\timeout.js:86
(anonymous) @ F:\classwork\madnet\node_modules\async\internal\initialParams.js:11
_dialWithTimeout @ F:\classwork\madnet\node_modules\libp2p-switch\src\limit-dialer\queue.js:86
_doWork @ F:\classwork\madnet\node_modules\libp2p-switch\src\limit-dialer\queue.js:41
DialQueue.queue.queue @ F:\classwork\madnet\node_modules\libp2p-switch\src\limit-dialer\queue.js:25
(anonymous) @ F:\classwork\madnet\node_modules\async\queue.js:10
process @ F:\classwork\madnet\node_modules\async\internal\queue.js:175
(anonymous) @ F:\classwork\madnet\node_modules\async\internal\queue.js:82
(anonymous) @ F:\classwork\madnet\node_modules\async\internal\setImmediate.js:27
runCallback @ timers.js:789
tryOnImmediate @ timers.js:751
processImmediate @ timers.js:722
Metadata
Metadata
Assignees
Labels
P3Low: Not priority right nowLow: Not priority right nowkind/supportA question or request for supportA question or request for supportstatus/readyReady to be workedReady to be worked