error when trying to cnnect to matic mainnet

[hshar7]

(node:21) UnhandledPromiseRejectionWarning: Error: Connection closed
    at /app/node_modules/mqtt/lib/client.js:124:29
    at Array.forEach (<anonymous>)
    at flushVolatile (/app/node_modules/mqtt/lib/client.js:122:24)
    at Duplex.<anonymous> (/app/node_modules/mqtt/lib/client.js:358:5)
    at Duplex.emit (events.js:315:20)
    at emitClose (/app/node_modules/ws/lib/stream.js:12:10)
    at processTicksAndRejections (internal/process/task_queues.js:83:21)
(node:21) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise r
ejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:21) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

eth mainnet is working fine

[senilshah]

I am facing similar issue, Do we need to change something in ('matic-mainnet.dagger.matic.network') url or is there any alternative way to complete it?

[jarrodlilkendey]

i'm facing this same issue. has anyone found a solution?

[hshar7]

Dagger is being deprecated, better to call web3js directly with an rpc endpoint from maticvigil

[arnold-almeida]

Thanks for the info @hshar7

May be worth putting a deprecation notice in the README and updating the website.

[0fatih]

@hshar7 do you know is there a web socket provider for matic?