Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
[bug] Can't update meteor behind a proxy on Linux! #689
Was trying to update meteor from 0.5.4 with:
behind a proxy, but it seems to give all the time:
This is quite unexpected since the system is setup correctly, wget and curl work too, and "npm", "bower" and all other dependency managers work without problems too behind the proxy.
Thanks in advance.
Thanks @aadrian! This is going to difficult to tackle without a reproduction. We will take a look at it when we get a chance but having a reproduction (maybe an EC2 instance that we can look at?) would both let us give it a high priority and would assist us in finding the problem.
does not work.
But what should I certainly do to help in solving problem? I'm not the pro in linux so I need some advices. However it worked for me something like 1-1.5 months ago. I didn't do anything, no changes in internet settings etc.
Hi @jagi, I don't know if this will help or not, but here goes: for someone to create a reproduction they would need to know Linux networking, but they don't need to know anything about Meteor. So maybe you could find someone to help you who has that skill set (a friend, or at a user's group if there's one in your area, or perhaps in a forum)...
(Asking here is kind of hit-or-miss... you might get lucky and be heard here by someone who knows Linux networking and happens to also be here looking at Meteor bugs... but you may find it easier to find someone in a forum that's more specific to Linux networking).
Ok I will try to find someone but one thing puzzles me, why it stopped working? Meteor team had to make some change that causes error so they're the most skilled to fix it. As I said I didn't change anything I've just updated Meteor and from this version it doesn't work. For me it looks like there is the problem with Meteor server because I can't even install fresh copy.
Hi. I have the same problem: "Failed to download manifest" on: meteor update.
curl https://install.meteor.com | sh
didn't work for me either. I looked in the script and there is a passage in the beginning that looks for an already installed meteor. And in case it finds one it executes: meteor update. Which results in:
"Failed to download manifest."
I downloaded the script, without executing, and deleted the first part (existing version check). Afterwards the above command worked. Well, almost. Now I have some issues regarding the placement of the executables.
@jagi: if curl is unable to download anything, look here: http://stackoverflow.com/questions/9445489/linux-curl-command-with-proxy
Update: after deletion of the old Meteor installation, the modified script worked and installed the most recent version of Meteor.
But I have problems downloading Npm modules, at least from private packages. Seems to hang on: tedious: updating npm dependencies -- tedious... I guess this has to do with the general proxy problem as well.
@Crenshinibon, the reason it works if you delete the existing version check is that you're completely sidestepping the meteor launcher script, which is the failure point here.
The node "request" library doesn't support automatically setting a proxy based on env vars; all clients need to do it themselves (I've opened a discussion about this here: request/request#595). npm works properly because it sets the proxy to the system proxy before calling out to request:
Curl and wget do the same.
There seem to be only two places where the 'request' library is currently used:
It's probably smart to use some sort of quick wrapper around the library to set the proxy unless there's another sensible place to query for the system proxy just once, though.
It's easy to globally set a default proxy with request as such, as well:
@spang, thanks for the clarification. I will try to go with the wrapper until a built-in solution is available.
Maybe I could change the "request" package itself to use the system proxy by default. Do you know where the NPM packages, that Meteor uses, are located? I looked through the folder structure but couldn't find it at first glimpse.
referenced this issue
Feb 17, 2015
I'm not behind the proxy.
This command works fine for https: