Meteor install fails due to bad CDN

help
1

Does anyone know a work around to install meteor in a location where their CDN fails even when attempted from a beefy server with tons of bandwidth speed (its NOT a connectivity issue at my end) ? Already tried trick to make meteor download from alternative location then scp tarball to Singapore which allows install to succeed however all subsequent meteor updates fail due to same bad CDN … see ticket for my traceroute output

time meteor --release 1.7.0.3   build --server https://speedofcausality.com  --verbose  --directory /cryptdata6/var/log/tmp/nefertiti01/loud_deploy/enduserPreEverything --server-only 
...
Local package version is up-to-date: srp@1.0.10
Local package version is up-to-date: standard-minifier-css@1.4.1
Local package version is up-to-date: standard-minifier-js@2.3.4
Local package version is up-to-date: tracker@1.2.0
Local package version is up-to-date: underscore@1.0.10
Local package version is up-to-date: url@1.2.0
Local package version is up-to-date: webapp-hashing@1.0.9
Downloading missing local versions of package aldeed:collection2@2.10.0 : [
'os.linux.x86_64' ]
Doing HTTP request:  GET
https://warehouse.meteor.com/builds/kYaz5QPx6xcYZ4F5A/1471932988050/PTuhBEP9gf/aldeed:collection2-2.10.0-os+web.browser+web.cordova.tgz
Downloading missing local versions of package aldeed:collection2-core@1.2.0 : [
'os.linux.x86_64' ]
Doing HTTP request:  GET
https://warehouse.meteor.com/builds/kYaz5QPx6xcYZ4F5A/1471930315782/Dyj2wRtaPF/aldeed:collection2-core-1.2.0-os+web.browser+web.cordova.tgz
Downloading missing local versions of package aldeed:schema-deny@1.1.0 : [
'os.linux.x86_64' ]

...
Request failed, 9 attempts left
Request failed, 9 attempts left
Request failed, 9 attempts left
Request failed, 9 attempts left
Request failed, 9 attempts left
...
Request failed 10 times: failing
Request failed 10 times: failing
Request failed 10 times: failing
=> Errors while initializing project:

While downloading aldeed:collection2@2.10.0...:
error: ETIMEDOUT
...
Request failed 10 times: failing
=> Errors while initializing project:

While downloading aldeed:collection2@2.10.0...:
error: ETIMEDOUT

While downloading aldeed:collection2-core@1.2.0...:
error: ETIMEDOUT

While downloading aldeed:schema-deny@1.1.0...:
error: ETIMEDOUT

While downloading aldeed:schema-index@1.1.1...:
error: ETIMEDOUT

While downloading aldeed:simple-schema@1.5.3...:
error: ETIMEDOUT

While downloading autoupdate@1.4.1...:
error: ETIMEDOUT

While downloading blaze@2.3.2...:
error: ETIMEDOUT

Solution could be something along lines of me updating my VPS which is running ubuntu 18.04 in Singapore to look to meteor as though I was in NY or similar ?

I have developers in Far East who are twiddling their thumbs while Rome burns

1 Like
2

If you have access to a Linux server that’s using another CDN, you could set up an SSH tunnel between that and your VPS.

I’ve never tried that with Meteor, but the technique works well with other services.

3

Also having this problem. Wish there were better documentation on how Atmosphere works and requirements for it. Data first approach is great, but if your network is glitchy or segmented, then we can’t even install. Need better offline support for times like these!

1 Like