Skip to main content

FAQ

image

FAQ

"Error: connect ENETUNREACH" or "Error: connect ETIMEDOUT" appears while using Arweave?​

TypeError: fetch failed
    at Object.fetch (node:internal/deps/undici/undici:11372:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    ...
  cause: AggregateError
      ...
    code: 'ETIMEDOUT',
    [errors]: [
      Error: connect ETIMEDOUT 118.184.26.113:443
          at createConnectionError (node:net:1634:14)
          at Timeout.internalConnectMultipleTimeout (node:net:1685:38)
          at listOnTimeout (node:internal/timers:575:11)
          at process.processTimers (node:internal/timers:514:7) {
        errno: -110,
        code: 'ETIMEDOUT',
        syscall: 'connect',
        address: '118.184.26.113',
        port: 443
      },
      Error: connect ENETUNREACH 2a03:2880:f102:183:face:b00c:0:25de:443 - Local (:::0)
          at internalConnectMultiple (node:net:1176:40)
          at Timeout.internalConnectMultipleTimeout (node:net:1687:3)
          at listOnTimeout (node:internal/timers:575:11)
          at process.processTimers (node:internal/timers:514:7) {
        errno: -101,
        code: 'ENETUNREACH',
        syscall: 'connect',
        address: '2a03:2880:f102:183:face:b00c:0:25de',
        port: 443
      }

This is usually a network or proxy issue. There is a way to set up a proxy.

  • Copy the following code into a js file such as proxy.js.

    import { ProxyAgent } from 'undici';

    if (process.env.HTTPS_PROXY) {
      const proxyAgent = new ProxyAgent(process.env.HTTPS_PROXY);
      const nodeFetch = globalThis.fetch
      globalThis.fetch = function (url, options) {
        return nodeFetch(url, { ...options, dispatcher: proxyAgent })
      }
    }

  • Add import "./proxy.js" to your .ts script.

  • Export HTTPS_PROXY=your-proxy in your terminal where you want to run the script.

"ConnectTimeoutError: Connect Timeout Error" appears while using Arweave?​

Error while trying to download chunked data for ...
TypeError: fetch failed
    at Object.fetch (node:internal/deps/undici/undici:11118:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    ...
  cause: ConnectTimeoutError: Connect Timeout Error
    ...
    code: 'UND_ERR_CONNECT_TIMEOUT'
    ...

This is usually a network or proxy issue. It's handled the same way as Error: connect ENETUNREACH.

"Error: Unable to get transaction offset: Not Found" appears while trying to download chunked data from Arweave?​

Error while trying to download chunked data for JqcyW81tMRZj3VWI7aQaTcGVhYaryGcnBFOkjSQrIKE
Error: Unable to get transaction offset: Not Found
    at Chunks.getTransactionOffset (..../node_modules/arweave/node/chunks.js:38:15)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Chunks.downloadChunkedData (..../node_modules/arweave/node/chunks.js:56:32)
    at async Transactions.getData (..../node_modules/arweave/node/transactions.js:120:20)
    at async getDataFromAR (..../node_modules/@padolabs/pado-ao-sdk/dist/padoarweave.js:46:18)
    at async getResult (..../node_modules/@padolabs/pado-ao-sdk/dist/index.js:149:20)
    at async main (..../dist/data_consumer.js:37:25)
Falling back to gateway cache for JqcyW81tMRZj3VWI7aQaTcGVhYaryGcnBFOkjSQrIKE

This is because data uploaded to Arweave by the data provider has not been packaged yet. You'll have to wait a while before you try again.

  • Unable to get transaction offset: Not Found means this transaction isn't done yet. (Also, this transaction is not yet visible in https://viewblock.io/arweave).
  • Falling back to gateway cache for ... means that the data is fetched from the gateway cache.