Vite7 server proxy AggregateError [ETIMEDOUT]

[jackqiu0123]

Describe the bug

Node v22.12
Vite 7.0.4
本地启动开发，proxy报错，如下图所示

package.json

Reproduction

https://stackblitz.com/edit/vitejs-vite-mxh9fcml?file=src%2Frequest.js,package.json,vite.config.js,src%2Fmain.jsx,src%2FApp.jsx,src%2FApp.css,index.html,yarn.lock&terminal=dev

Steps to reproduce

yarn
yarn dev
https://dev.xxx.com/

System Info

System:
    OS: macOS 15.5
    CPU: (8) arm64 Apple M1 Pro
    Memory: 133.55 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.12.0 - ~/.nvm/versions/node/v22.12.0/bin/node
    Yarn: 1.22.22 - /opt/homebrew/bin/yarn
    npm: 10.9.0 - ~/.nvm/versions/node/v22.12.0/bin/npm
    pnpm: 10.12.4 - /opt/homebrew/bin/pnpm
  Browsers:
    Brave Browser: 108.1.46.144
    Chrome: 138.0.7204.101
    Chrome Canary: 140.0.7288.0
    Safari: 18.5
  npmPackages:
    @vitejs/plugin-basic-ssl: ^2.1.0 => 2.1.0 
    @vitejs/plugin-react: ^4.5.2 => 4.6.0 
    vite: ^7.0.2 => 7.0.4

Used Package Manager

yarn

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[Binaryify]

add this in your vite api proxy config, the reason should be your network don't support ipv6

import https from 'https'; 
.....

'/api': {
 ...
  secure: false, // allow proxy to  HTTPS
  agent: new https.Agent({
    family: 4, // force use  IPv4，disable IPv6
    keepAlive: true,
  }),

[rawbin-]

Vite 8 同样的问题 不是IPv6
ERROR 12:39:22 [vite] http proxy error: /common-static/react.18.2.0.min-860f1d37ec17b010c94069b99a49ae7b.js 12:39:22
AggregateError [ETIMEDOUT]:
at internalConnectMultiple (node:net:1134:18)
at afterConnectMultiple (node:net:1715:7)