Unable to create new meteor 3 projects

[santo74]

Whenever I specify any v3 release during project creation (alpha, beta or rc), I get connection timeout errors:

$  meteor create my-v3-project --release 3.0-rc.0
Using react skeleton
Something has happened while creating your app using git clone.
Will use cached version of skeletons.
Error message:  Using release option
AggregateError                                
    at internalConnectMultiple (node:net:1114:18)
    at internalConnectMultiple (node:net:1177:5)
    at Timeout.internalConnectMultipleTimeout (node:net:1687:3)
    at listOnTimeout (node:internal/timers:575:11)
    at processTimers (node:internal/timers:514:7) {
  code: 'ETIMEDOUT',
  [errors]: [
    Error: connect ETIMEDOUT 188.114.96.0:443
        at createConnectionError (node:net:1634:14)
        at Timeout.internalConnectMultipleTimeout (node:net:1685:38)
        at listOnTimeout (node:internal/timers:575:11)
        at processTimers (node:internal/timers:514:7) {
      errno: -110,
      code: 'ETIMEDOUT',
      syscall: 'connect',
      address: '188.114.96.0',
      port: 443
    },
    Error: connect ENETUNREACH 2a06:98c1:3120:::443 - Local (:::0)
        at internalConnectMultiple (node:net:1176:40)
        at Timeout.internalConnectMultipleTimeout (node:net:1687:3)
        at listOnTimeout (node:internal/timers:575:11)
        at processTimers (node:internal/timers:514:7) {
      errno: -101,
      code: 'ENETUNREACH',
      syscall: 'connect',
      address: '2a06:98c1:3120::',
      port: 443
    },
    Error: connect ETIMEDOUT 188.114.97.0:443
        at createConnectionError (node:net:1634:14)
        at Timeout.internalConnectMultipleTimeout (node:net:1685:38)
        at listOnTimeout (node:internal/timers:575:11)
        at processTimers (node:internal/timers:514:7) {
      errno: -110,
      code: 'ETIMEDOUT',
      syscall: 'connect',
      address: '188.114.97.0',
      port: 443
    },
    Error: connect ENETUNREACH 2a06:98c1:3121:::443 - Local (:::0)
        at internalConnectMultiple (node:net:1176:40)
        at Timeout.internalConnectMultipleTimeout (node:net:1687:3)
        at listOnTimeout (node:internal/timers:575:11)
        at processTimers (node:internal/timers:514:7) {
      errno: -101,
      code: 'ENETUNREACH',
      syscall: 'connect',
      address: '2a06:98c1:3121::',
      port: 443
    }
  ]
}

With 2.x release (or without a specific release, the project gets created without any errors:

$ meteor create my-v2-project --release 2.15
Using react skeleton
Created a new Meteor app in 'my-v2-project'.        

To run your new app:                          
  cd my-v2-project                                  
  meteor                                      
                                              
If you are new to Meteor, try some of the learning resources here:
  https://www.meteor.com/tutorials            
                                              
When you’re ready to deploy and host your new Meteor application, check out Cloud:
  https://www.meteor.com/cloud

Versions:

$  node -v
v20.12.2

$  meteor node -v
v14.21.4

$  meteor --version
Meteor 2.15

The OS is Linux Mint 20.3

Since I'm starting a completely new project I want to start with v3 instead of v2

[denihs]

Hi,

I just tried to reproduce this on my machine. This is my environment:

$  node -v
v20.12.2

$ npm -v
10.5.0

$  meteor node -v
v14.21.4

$  meteor --version
Meteor 2.15

So it's the same as yours. And still, I was able to install everything without any problems:

The difference from your setup is that I'm using Ubuntu OS.

I'd say it's something related to your network, but as you said, it works for version 2.15...

But still, I can't think of another reason. Do you use a VPN or have any direct configuration on your network?

Also, do you have any other network you can try out?

[santo74]

Hi,

I tried on 2 other systems, one running Zorin OS and one running Ubuntu.
The Zorin OS system is in the same network, the Ubuntu system is in a completely different network.

On Zorin OS it initially failed as well, but the second time (1 minute later) it worked:

$  meteor create meteor3 --release 3.0-rc.0
Using react skeleton                                                               
Something has happened while creating your app using git clone.
Will use cached version of skeletons.
Error message:  Using release option
Error: read ECONNRESET                                                             
    at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20)
    at TLSWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
  errno: -104,
  code: 'ECONNRESET',
  syscall: 'read'
}

$  meteor create meteor-v3 --release 3.0-rc.0
Using react skeleton                          
Something has happened while creating your app using git clone.
Will use cached version of skeletons.
Error message:  Using release option
Created a new Meteor app in 'meteor-v3'.                                              

To run your new app:                          
  cd meteor-v3                                   
  meteor                                      
                                              
If you are new to Meteor, try some of the learning resources here:
  https://www.meteor.com/tutorials            
                                              
When you’re ready to deploy and host your new Meteor application, check out Cloud:
  https://www.meteor.com/cloud

On Ubuntu it worked immediately:

$  meteor create meteor3 --release 3.0-rc.0
Using react skeleton                                                               
Something has happened while creating your app using git clone.
Will use cached version of skeletons.
Error message:  Using release option
Created a new Meteor app in 'meteor3'.        

To run your new app:                          
  cd meteor3                                  
  meteor                                      
                                              
If you are new to Meteor, try some of the learning resources here:
  https://www.meteor.com/tutorials            
                                              
When you’re ready to deploy and host your new Meteor application, check out Cloud:
  https://www.meteor.com/cloud

So I decided to try again on the initial Mint system.
The result was that it failed again the first time, but the second time it worked:

$  meteor create meteor3 --release 3.0-rc.0
Using react skeleton                          
Something has happened while creating your app using git clone.
Will use cached version of skeletons.
Error message:  Using release option
AggregateError                                
    at internalConnectMultiple (node:net:1114:18)
    at internalConnectMultiple (node:net:1177:5)
    at Timeout.internalConnectMultipleTimeout (node:net:1687:3)
    at listOnTimeout (node:internal/timers:575:11)
    at processTimers (node:internal/timers:514:7) {
  code: 'ETIMEDOUT',
  [errors]: [
    Error: connect ETIMEDOUT 104.21.26.159:443
        at createConnectionError (node:net:1634:14)
        at Timeout.internalConnectMultipleTimeout (node:net:1685:38)
        at listOnTimeout (node:internal/timers:575:11)
        at processTimers (node:internal/timers:514:7) {
      errno: -110,
      code: 'ETIMEDOUT',
      syscall: 'connect',
      address: '104.21.26.159',
      port: 443
    },
    Error: connect ENETUNREACH 2a06:98c1:3121:::443 - Local (:::0)
        at internalConnectMultiple (node:net:1176:40)
        at Timeout.internalConnectMultipleTimeout (node:net:1687:3)
        at listOnTimeout (node:internal/timers:575:11)
        at processTimers (node:internal/timers:514:7) {
      errno: -101,
      code: 'ENETUNREACH',
      syscall: 'connect',
      address: '2a06:98c1:3121::',
      port: 443
    },
    Error: connect ETIMEDOUT 172.67.137.45:443
        at createConnectionError (node:net:1634:14)
        at Timeout.internalConnectMultipleTimeout (node:net:1685:38)
        at listOnTimeout (node:internal/timers:575:11)
        at processTimers (node:internal/timers:514:7) {
      errno: -110,
      code: 'ETIMEDOUT',
      syscall: 'connect',
      address: '172.67.137.45',
      port: 443
    },
    Error: connect ENETUNREACH 2a06:98c1:3120:::443 - Local (:::0)
        at internalConnectMultiple (node:net:1176:40)
        at Timeout.internalConnectMultipleTimeout (node:net:1687:3)
        at listOnTimeout (node:internal/timers:575:11)
        at processTimers (node:internal/timers:514:7) {
      errno: -101,
      code: 'ENETUNREACH',
      syscall: 'connect',
      address: '2a06:98c1:3120::',
      port: 443
    }
  ]
}

$  meteor create meteor-v3 --release 3.0-rc.0
Using react skeleton                          
Something has happened while creating your app using git clone.
Will use cached version of skeletons.
Error message:  Using release option
Created a new Meteor app in 'meteor-v3'.      

To run your new app:                          
  cd meteor-v3                                
  meteor                                      
                                              
If you are new to Meteor, try some of the learning resources here:
  https://www.meteor.com/tutorials            
                                              
When you’re ready to deploy and host your new Meteor application, check out Cloud:
  https://www.meteor.com/cloud

So in the end I was able to create a meteor 3 project on all 3 systems, but it can't be ignored there are severe connection issues.

Some notable observations:

• While I didn't have any connection issues on the Ubuntu system, it took a relatively long time to create the project. That is considerably longer than on the 2 other systems (when it worked)
• While both the Mint and Zorin OS systems failed because of connection issues, the error was different on both systems
• The Mint system is my main development environment and I never experience any other connection issues on that system, even not when I am installing and updating other npm packages (which happens regularly).

[lucasavila00]

I'm also getting these on ubuntu.

I was able to fix it by upgrading to RC1 using a cached meteor install...