We're also affected by this bug.

Cheers! I am affected with same bug, but can only reproduce it at Node 20.10, fallback to Node 18.18 works fine.

The cause of this issue is the way follow-redirects implements timeout. It has problems when dealing with keep-alive connections. A simple fix is to remove the timeout event handler when the request finishes, but I'm not sure this will work for all use-cases, as that library is mostly geared towards earlier node versions.

Same issue here. Is there any workaround except a dumb retry?

Same issue here. Is there any workaround except a dumb retry?

@NaZaRKIN123 Something like this would work:

axios.defaults.httpAgent = new Agent({ keepAlive: false });

I can confirm that the workaround provided by @snarky-puppy worked for us 🙏

Thanks for the detail investigation. The keepAlive is needed on my project in order to reduce latency
In case we disable follow-redirects, would that be solved?

+1

+1

Cheers! I am affected with same bug, but can only reproduce it at Node 20.10, fallback to Node 18.18 works fine.

This is because of #6536. Short summary: Node.js changed its default Keep-Alive behavior after Node.js 18.

I try following code in next.js _app.tsx, but not worked:

// _app.tsx
if (typeof window === 'undefined') {
  /**
   * @see https://github.com/axios/axios/issues/6113#issuecomment-1909291937
   */
  async function fixAxiosKeepAlive() {
    const { default: axios } = await import('axios');
    const { Agent } = await import('https');
    axios.defaults.httpAgent = new Agent({ keepAlive: false });
  }
  fixAxiosKeepAlive();
}

Because of this issue, we have to revert from node 20 to 18, or we may try to remove the axios from our project.

axios.defaults.httpsAgent = new Agent({ keepAlive: false });

@tjx666 you should replace httpsAgent (and httpAgent too if you use http, but it's a different class)

+1