Hello!
The update for meteor is not downloading.
After waiting for the download to stop at 0%, it remains frozen. The logs indicate that you are online. What is the url for requesting the parts?
The system administrator asks for the URL and port number to ensure that the request is not blocked by our firewall.
I think you should configure your firewall to allow these:
URL: https://static.meteor.com
Port: 443 (HTTPS)
It’s this endpoint the one used as part of the install script and the CLI as far as I know. Usually looking a specific version url like: https://static.meteor.com/packages-bootstrap/${RELEASE}/meteor-bootstrap-${PLATFORM}.tar.gz (check https://install.meteor.com script).
Can you write an example url without variables for the ubuntu linux platform?
Or are there any logs with the exact link where the update package is downloaded?
URL: https://static.meteor.com
Port: 443 (HTTPS)
The website itself opens, and it displays XML that says there is no access.
This means that there are no restrictions on downloading the entire website. It is possible that a firewall is blocking a specific file type or executable script from being downloaded.
https://static.meteor.com/packages-bootstrap/3.2.2/meteor-bootstrap-os.linux.x86_64.tar.gz
For me this url works well and tries to download it. Does it for you?
Check if after the firewall configuration to exclude that domain and port it changes for you.
Thank you!
The download started, but the speed was 0. It seems that the firewall is not blocking the file, but another security system is limiting its speed. I turned on the VPN, and the file was successfully downloaded. However, I am unsure of the exact stage or system that is limiting the speed.
Is it possible to install a file manually by downloading it from another computer?
If you extract meteor-bootstrap-os.linux.x86_64.tar.gz, you’ll see it includes Meteor’s global context as a .meteor folder. If you replace your existing global context with this one (~/.meteor on Unix-like systems, %LOCALAPPDATA%\.meteor on Windows), that should be enough to make it work. Make sure your PATH resolves to that global .meteor install, since it contains the meteor binary.
That said, it would be good to fix whatever is blocking downloads from that origin. If you’re managing Atmosphere package versions for Meteor, you’ll likely run into the same issue again when fetching or updating packages. Your system should properly enable download from Meteor origin for proper work experience.
Which OS are you using? And what firewall or network security software is in place?
