Anyone else having issue trying to install or update meteor?

help
1

Today I started having an issue and I decided t uninstall meteor and reinstall it. Now I cant install it because of an error when running npx meteor.

I tried in 2 different machines with no luck. Is this happening to anyone else?

2

hey @pmogollon!

Weird. What’s the error?

3

Hey Gabs,

Im getting this error on the console on all the installation options. I dont know what else to do, none of my dev machines can run a meteor project anymore.

=> Arch: os.osx.arm64
=> Meteor Release: 3.3.2
Downloading |░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░| 0%/xxxxxx/.npm/_npx/a161db0e9e033064/node_modules/meteor/install.js:63
  throw err;
  ^

Error: socket hang up
    at TLSSocket.socketCloseListener (node:_http_client:491:27)
    at TLSSocket.emit (node:events:530:35)
    at node:net:351:12
    at TCP.done (node:_tls_wrap:650:7)
Emitted 'error' event on b instance at:
    at /xxxx/.npm/_npx/a161db0e9e033064/node_modules/node-downloader-helper/dist/index.js:1:12756
    at <anonymous> {
  code: 'ECONNRESET'
}

Node.js v22.15.0
4

This was a pain in the ass. At last I ended up customizing the script from install.meteor.com to use a local path to the tarball. It was the only solution that worked.

5

Screenshot 2025-09-12 at 16.55.55
Screenshot 2025-09-12 at 16.55.551852×1142 166 KB

I attempted to recreate the issue, but I could install Meteor successfully.

Anyway, I already shared this issue with our Open Source team and DevOps team.

6

Working into 5g connetion
did you try use another internet connection? i mean, you are getting a socket close error ECONNRESET, it can be the newtwork issue, interenet, vpn, firewall… (maybe maybe)

Screenshot 2025-09-12 at 5.04.18 PM
Screenshot 2025-09-12 at 5.04.18 PM1846×1442 247 KB

but when I turn off the wifi while its downloading, I get the another issue

Screenshot 2025-09-12 at 5.07.43 PM
Screenshot 2025-09-12 at 5.07.43 PM1528×708 87 KB

I see you are using mac, what about desactivate /ipv6? I solved a few issues doing it

another option is doing it via npm

NODE_OPTIONS="--dns-result-order=ipv4first" npx meteor
7

@hschmaiske @italojs, yes this was a very weird issue. I still cant curl the tarball but i can download it with chrome.

I think this could be an issue with my network, but even when I tried with 5g from my phone it didnt work.

I did add a vpn on wednesday, but is not active. It is possible that is something with a cache or something, I did flush the dns cache but didnt work.

If I run

openssl s_client -connect static.meteor.com:443 -servername static.meteor.com -tls1_2 -brief

It gets stuck. Probably an issue with my version of osx, which was updated recently, but that doesnt make much sense because my linux machine had the same issue.

I dont have ipv6 active.

Im not sure how to debug this, if you guys have any ideas let me know. Thanks.

8

On linux I get this.

wanchope@wanchope:~$ npx meteor
=> Arch: os.linux.x86_64
=> Meteor Release: 3.3.2
Downloading |░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░| 0%/home/wanchope/.npm/_n3
  throw err;
  ^

AggregateError [ETIMEDOUT]: 
    at internalConnectMultiple (node:net:1116:18)
    at internalConnectMultiple (node:net:1184:5)
    at Timeout.internalConnectMultipleTimeout (node:net:1710:5)
    at listOnTimeout (node:internal/timers:583:11)
    at process.processTimers (node:internal/timers:519:7)
Emitted 'error' event on b instance at:
    at /home/wanchope/.npm/_npx/a161db0e9e033064/node_modules/node-downloader-h6
    at <anonymous>
    at process.processTicksAndRejections (node:internal/process/task_queues:95:{
  code: 'ETIMEDOUT',
  [errors]: [
    Error: connect ETIMEDOUT 104.21.16.1:443
        at createConnectionError (node:net:1646:14)
        at Timeout.internalConnectMultipleTimeout (node:net:1705:38)
        at listOnTimeout (node:internal/timers:583:11)
        at process.processTimers (node:internal/timers:519:7) {
      errno: -110,
      code: 'ETIMEDOUT',
      syscall: 'connect',
      address: '104.21.16.1',
      port: 443
    },
    Error: connect ENETUNREACH 2606:4700:3030::6815:3001:443 - Local (:::0)
        at internalConnectMultiple (node:net:1180:16)
        at Timeout.internalConnectMultipleTimeout (node:net:1710:5)
        at listOnTimeout (node:internal/timers:583:11)
        at process.processTimers (node:internal/timers:519:7) {
      errno: -101,
      code: 'ENETUNREACH',
      syscall: 'connect',
      address: '2606:4700:3030::6815:3001',
      port: 443
    },
    Error: connect ETIMEDOUT 104.21.64.1:443
        at createConnectionError (node:net:1646:14)
        at Timeout.internalConnectMultipleTimeout (node:net:1705:38)
        at listOnTimeout (node:internal/timers:583:11)
        at process.processTimers (node:internal/timers:519:7) {
      errno: -110,
      code: 'ETIMEDOUT',
      syscall: 'connect',
      address: '104.21.64.1',
      port: 443
    },
    Error: connect ENETUNREACH 2606:4700:3030::6815:5001:443 - Local (:::0)
        at internalConnectMultiple (node:net:1180:16)
        at Timeout.internalConnectMultipleTimeout (node:net:1710:5)
        at listOnTimeout (node:internal/timers:583:11)
        at process.processTimers (node:internal/timers:519:7) {
      errno: -101,
      code: 'ENETUNREACH',
      syscall: 'connect',
      address: '2606:4700:3030::6815:5001',
      port: 443
    },
    Error: connect ETIMEDOUT 104.21.112.1:443
        at createConnectionError (node:net:1646:14)
        at Timeout.internalConnectMultipleTimeout (node:net:1705:38)
        at listOnTimeout (node:internal/timers:583:11)
        at process.processTimers (node:internal/timers:519:7) {
      errno: -110,
      code: 'ETIMEDOUT',
      syscall: 'connect',
      address: '104.21.112.1',
      port: 443
    },
    Error: connect ENETUNREACH 2606:4700:3030::6815:2001:443 - Local (:::0)
        at internalConnectMultiple (node:net:1180:16)
        at Timeout.internalConnectMultipleTimeout (node:net:1710:5)
        at listOnTimeout (node:internal/timers:583:11)
        at process.processTimers (node:internal/timers:519:7) {
      errno: -101,
      code: 'ENETUNREACH',
      syscall: 'connect',
      address: '2606:4700:3030::6815:2001',
      port: 443
    },
    Error: connect ETIMEDOUT 104.21.96.1:443
        at createConnectionError (node:net:1646:14)
        at Timeout.internalConnectMultipleTimeout (node:net:1705:38)
        at listOnTimeout (node:internal/timers:583:11)
        at process.processTimers (node:internal/timers:519:7) {
      errno: -110,
      code: 'ETIMEDOUT',
      syscall: 'connect',
      address: '104.21.96.1',
      port: 443
    },
    Error: connect ENETUNREACH 2606:4700:3030::6815:1001:443 - Local (:::0)
        at internalConnectMultiple (node:net:1180:16)
        at Timeout.internalConnectMultipleTimeout (node:net:1710:5)
        at listOnTimeout (node:internal/timers:583:11)
        at process.processTimers (node:internal/timers:519:7) {
      errno: -101,
      code: 'ENETUNREACH',
      syscall: 'connect',
      address: '2606:4700:3030::6815:1001',
      port: 443
    },
    Error: connect ETIMEDOUT 104.21.80.1:443
        at createConnectionError (node:net:1646:14)
        at Timeout.internalConnectMultipleTimeout (node:net:1705:38)
        at listOnTimeout (node:internal/timers:583:11)
        at process.processTimers (node:internal/timers:519:7) {
      errno: -110,
      code: 'ETIMEDOUT',
      syscall: 'connect',
      address: '104.21.80.1',
      port: 443
    },
    Error: connect ENETUNREACH 2606:4700:3030::6815:7001:443 - Local (:::0)
        at internalConnectMultiple (node:net:1180:16)
        at Timeout.internalConnectMultipleTimeout (node:net:1710:5)
        at listOnTimeout (node:internal/timers:583:11)
        at process.processTimers (node:internal/timers:519:7) {
      errno: -101,
      code: 'ENETUNREACH',
      syscall: 'connect',
      address: '2606:4700:3030::6815:7001',
      port: 443
    },
    Error: connect ETIMEDOUT 104.21.48.1:443
        at createConnectionError (node:net:1646:14)
        at Timeout.internalConnectMultipleTimeout (node:net:1705:38)
        at listOnTimeout (node:internal/timers:583:11)
        at process.processTimers (node:internal/timers:519:7) {
      errno: -110,
      code: 'ETIMEDOUT',
      syscall: 'connect',
      address: '104.21.48.1',
      port: 443
    },
    Error: connect ENETUNREACH 2606:4700:3030::6815:4001:443 - Local (:::0)
        at internalConnectMultiple (node:net:1180:16)
        at Timeout.internalConnectMultipleTimeout (node:net:1710:5)
        at listOnTimeout (node:internal/timers:583:11)
        at process.processTimers (node:internal/timers:519:7) {
      errno: -101,
      code: 'ENETUNREACH',
      syscall: 'connect',
      address: '2606:4700:3030::6815:4001',
      port: 443
    },
    Error: connect ETIMEDOUT 104.21.32.1:443
        at createConnectionError (node:net:1646:14)
        at Timeout.internalConnectMultipleTimeout (node:net:1705:38)
        at listOnTimeout (node:internal/timers:583:11)
        at process.processTimers (node:internal/timers:519:7) {
      errno: -110,
      code: 'ETIMEDOUT',
      syscall: 'connect',
      address: '104.21.32.1',
      port: 443
    },
    Error: connect ENETUNREACH 2606:4700:3030::6815:6001:443 - Local (:::0)
        at internalConnectMultiple (node:net:1180:16)
        at Timeout.internalConnectMultipleTimeout (node:net:1710:5)
        at listOnTimeout (node:internal/timers:583:11)
        at process.processTimers (node:internal/timers:519:7) {
      errno: -101,
      code: 'ENETUNREACH',
      syscall: 'connect',
      address: '2606:4700:3030::6815:6001',
      port: 443
    }
  ]
}

Node.js v22.5.0
9

After more digging it looks like its an issue at the ISP level when resolving an edge ip for static.meteor.com.

10

it seems like i cant use shadcn with meteor and even using aliases @ did the babel config not working is there a way around it for me to use this always getting this error Unable to resolve some modules:

“@/lib/utils” in
/C/Users/USER/Dev/my-housing/imports/ui/components/ui/label.jsx
(web.browser)
“@radix-ui/react-switch” in
/C/Users/USER/Dev/my-housing/imports/ui/components/ui/switch.jsx
(web.browser)
“swiper/react/swiper-react.js” in
/C/Users/USER/Dev/my-housing/imports/ui/bodyComponent/image-componet.jsx
(web.browser)

“swiper/modules/navigation/navigation.min.css”
in
/C/Users/USER/Dev/my-housing/imports/ui/bodyComponent/image-componet.jsx
(web.browser)

“swiper/modules/pagination/pagination.min.css”
in
/C/Users/USER/Dev/my-housing/imports/ui/bodyComponent/image-componet.jsx
(web.browser)
“swiper/react” in
/C/Users/USER/Dev/my-housing/imports/ui/shortlet/shortlet-house.jsx
(web.browser)
“swiper/css” in
/C/Users/USER/Dev/my-housing/imports/ui/shortlet/shortlet-house.jsx
(web.browser)
“swiper/css/navigation” in
/C/Users/USER/Dev/my-housing/imports/ui/shortlet/shortlet-house.jsx
(web.browser)
“swiper/css/pagination” in
/C/Users/USER/Dev/my-housing/imports/ui/shortlet/shortlet-house.jsx