Closed
Description
Description
Our tests use a proxy server to connect to a site on the public internet. Starting on 2025-05-14T19:23:15, those tests started to fail with network connection errors. The error messages look like this:
AggregateError [ETIMEDOUT]:
at internalConnectMultiple (node:net:1139:18)
at internalConnectMultiple (node:net:1139:18)
at internalConnectMultiple (node:net:1215:5)
at Timeout.internalConnectMultipleTimeout (node:net:1741:5)
at listOnTimeout (node:internal/timers:590:11)
at process.processTimers (node:internal/timers:523:7)
at internalConnectMultiple (node:net:1215:5)
at Timeout.internalConnectMultipleTimeout (node:net:1741:5)
at listOnTimeout (node:internal/timers:590:11)
at process.processTimers (node:internal/timers:523:7) {
code: 'ETIMEDOUT',
[errors]: [
Error: connect ETIMEDOUT XXX.XXX.XXX.XXX:443
at createConnectionError (node:net:1677:14)
at Timeout.internalConnectMultipleTimeout (node:net:1736:38)
at listOnTimeout (node:internal/timers:590:11)
at process.processTimers (node:internal/timers:523:7) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: 'XXX.XXX.XXX.XXX',
port: 443
},
Error: connect ENETUNREACH [260](https://github.com/. . . )X:XXXX::XXXX:XXXX:443 - Local (:::0)
at internalConnectMultiple (node:net:1211:16)
at Timeout.internalConnectMultipleTimeout (node:net:1741:5)
at listOnTimeout (node:internal/timers:590:11)
at process.processTimers (node:internal/timers:523:7) {
errno: -101,
code: 'ENETUNREACH',
syscall: 'connect',
address: 'XXXX:XXXXX::XXXX:XXX',
port: 443
},
Error: connect ETIMEDOUT XXX.XXX.XXX.XXX:443
at createConnectionError (node:net:1677:14)
at Timeout.internalConnectMultipleTimeout (node:net:1736:38)
at listOnTimeout (node:internal/timers:590:11)
at process.processTimers (node:internal/timers:523:7) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: 'XXX.XXX.XXX.XXX',
port: 443
},
Error: connect ENETUNREACH XXXX:XXXX::XXXX:XXX:443 - Local (:::0)
at internalConnectMultiple (node:net:1211:16)
at Timeout.internalConnectMultipleTimeout (node:net:1741:5)
at listOnTimeout (node:internal/timers:590:11)
at process.processTimers (node:internal/timers:523:7) {
errno: -101,
code: 'ENETUNREACH',
syscall: 'connect',
address: 'XXXX:XXXX::XXXX:[297](https://github.com/....)',
port: 443
}
]
}
Platforms affected
- Azure DevOps
- GitHub Actions - Standard Runners
- GitHub Actions - Larger Runners
Runner images affected
- Ubuntu 22.04
- Ubuntu 24.04
- macOS 13
- macOS 13 Arm64
- macOS 14
- macOS 14 Arm64
- macOS 15
- macOS 15 Arm64
- Windows Server 2019
- Windows Server 2022
- Windows Server 2025
Image version and build link
Image: ubuntu-24.04
Version: 20250511.1.0
We have also tried this on
Image: ubuntu-22.04
Version: 20250511.1.0
This is happening on a private repository
Is it regression?
No
Expected behavior
Attempts to proxy requests to public website should succeed.
Actual behavior
Attempts to proxy requests to public website time out.
Repro steps
- Run github actions that use vite-proxy to access public resources.
- Proxy requests time out.