Cannot install behind a proxy

[jaing]

Cannot install behind a proxy. Please create an installer with all the files.

[coreybutler]

This need is noted for Windows. This will require a new installer... so I'll get this released as soon as I can.

[adyba]

Not sure it has anything with proxy. Have no proxy and can't install it either (Windows).
Complete install file would be fine.

[coreybutler]

Can you clarify the actual problem? My original perception was you could download the install file, but the actual installation process failed behind the proxy. One of the steps the installer performs is downloading node-webkit, which is a requirement. It is possible the proxy is rejecting the download.

If there is no proxy and you're connected to the internet, then the installation should work, assuming you're installing with admin privileges.

[jaing]

Without proxy its working on my home pc but at work im not able to install
it because installer is not able to download dependecies. Setting up env
variables HTTP_PROXY and HTTPS_PROXY doesnt help either :(

2014-07-03 18:57 GMT+02:00 Corey Butler notifications@github.com:

Can you clarify the actual problem? My original perception was you could
download the install file, but the actual installation process failed
behind the proxy. One of the steps the installer performs is downloading
node-webkit, which is a requirement. It is possible the proxy is rejecting
the download.

If there is no proxy and you're connected to the internet, then the
installation should work, assuming you're installing with admin privileges.

—
Reply to this email directly or view it on GitHub
#44 (comment).

[adyba]

98% windows installation works fine, then credits.html and about three dll's fail to install
Error code:0x800C00E

[coreybutler]

@jaing - Thanks, the issue is clear now. I should be able to make a full installer in the next minor version release.

@adyba - which version of Windows are you running?

[adyba]

Sorry for this delay, If I do remember the attempt was on W7

[adyba]

Pliiiz, we need the instaler

[coreybutler]

@adyba If the install is working "98% of the way", then this is not a proxy issue. It's a permissions problem on your PC. You have to run the installation as an admin user. If you're attempting to install to a directory within C:\Program Files or C:\Program Files (x86), then you'll need elevated rights.

[adyba]

@coreybutler I have already tried that. I have sudo access and the installer was launched with admin privileges. The Windows installer is overcomplicated and it is trying to be very fancy, run extra tasks instead of simple downloading and copying stuff which results in missing Node Webkit runtime environment.
The quick fix is to install Node Webkit for Windows separately and copy needed files from Node Webkit root folder into Fenix root. Even renamed fenix.exe (which actually is nw.exe with fancy icon) doesn't work. Just after I run the vanila nw.exe instead, the server has started (but it could be a version conflict as I have downloaded really fresh NW).

[coreybutler]

@adyba - the installer just downloads node-webkit to the temp directory and copies the required files to the user-specified installation directory. It attempts rename nw.exe to fenix.exe and associate the fenix icon with it... that's it. This is not a proxy issue though, so it would be best to open a new issue.

[jeffshelly]

Same problem here, I have admin credentials to my PC at work. I can download the install file, but the install process never gets past downloading a file called nw.zip with a status of "Cannot connect"

We do have a proxy that may be preventing the install app to pull the required files.

[ghost]

Count me in on the proxy problem. Installer fails while trying to download a zip file

[coreybutler]

Fenix 3 has a new installer, and all application dependencies bundled in the release package (i.e. the installer doesn't need to download node-webkit separately anymore). I'll close this once we're finished testing the new installer.

[amiramix]

Any update on this? Currently I can't install because of HTTP 403 error early in the installation process, likely due to a corporation proxy restricting access to some website.

[coreybutler]

There won't really be a fix for this in Fenix 2. Bottom line: we don't have time for it (there are only 2 of us, the other has a full time job on top of this). Our focus for the last 9 months has been on Fenix 3. We're very near a release, but there are still a few blocking points (mostly administrative) we need to get through before we can release. We've finished the core code, but our DUNS number was just activated this week, which is a prerequisite for obtaining our code-signing certificates. The certificates are a prerequisite for the build process, which is a prerequisite for the auto-update capabilities.... it feels like a game of dominos here ;-) We're hoping to get a preview release out before the end of the month (the download link will be sent to the mailing list).

Here's a preview:

[amiramix]

That's great, but the only thing that's needed to address this issue is an installer which has all dependencies bundled in. There are only few applications that require downloading additional data during the installation process and even if they do, they usually handle proxy properly (e.g. use the IE settings).

[coreybutler]

@amiramix - easier said than done. Installers are finicky. The existing installer does use proxy settings specified at the OS level, but that doesn't stop the proxy from blocking the download site (the old node-webkit page). That's something that would need to be configured in the proxy routing table.

For anyone who really needs this now, it might be worth following the manual Linux installation instructions. Even though it says it's for Linux, it's really just a generic installation process... it will work on Win/OSX too.