Skip to main content
Question

Trying to read board data in typescript, but found error

  • September 23, 2025
  • 1 reply
  • 23 views
Z


     
FetchError: request to https://api.monday.com/v2 failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (/projects//node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:524:28)
    at ClientRequest.emit (node:domain:489:12)
    at emitErrorEvent (node:_http_client:101:11)
    at TLSSocket.socketErrorListener (node:_http_client:504:5)
    at TLSSocket.emit (node:events:524:28)
    at TLSSocket.emit (node:domain:489:12)
    at emitErrorNT (node:internal/streams/destroy:169:8)
    at emitErrorCloseNT (node:internal/streams/destroy:128:3)
    at processTicksAndRejections (node:internal/process/task_queues:82:21) {
  type: 'system',
  errno: 'ECONNRESET',
  code: 'ECONNRESET'
}

    1 reply

    dvdsmpsn
    Forum|alt.badge.img+1
    • dvdsmpsn
    • Participating Frequently
    • September 23, 2025

    I’m guessing that there was a problem in Monday’s end. Maybe an outage? Just try again?

    The error “read ECONNRESET” happens when the server unexpectedly closes the connection while a client (like a Node.js app) is trying to make a request.

    Possible Causes & Fixes

    1. VPN/Network Issues
      • If you’re using a VPN, it can interfere with network connections. Try disabling it if the endpoint is public.
      • Conversely, if the API requires VPN, make sure the VPN is active and properly configured.
    2. Server Overload or Resource Constraints
      • If the server is low on CPU or memory, it may drop connections.
    3. Incorrect Request Configuration
      • Mistakes like wrong HTTP method, wrong host or protocol (http/https), malformed headers or JSON body, invalid query params, etc.
      • Make sure there are no typos, incorrect domain names, invalid characters, missing authentication if needed.
    4. Bad Internet Connection
      • Poor connectivity on the client side can cause dropped connections. Try switching networks.
    5. Timeouts Set Too Low
      • If the timeout for connections or responses is too short, the server may kill the connection before finishing.
      • E.g., databases like MySQL have timeouts like wait_timeout; servers often allow you to set socket/connection timeout values.
    6. Missing Error Handling
      • In Node.js/Express, you should add a global or catch-all error handler to log errors.
      • Also, make sure server settings (like server.timeout, server.maxConnections) are reasonable.
    Terms & ConditionsCookie settingsAccessibility statement