Hi everybody
I’m currently not able to login (via Forge) and i suspect it’s because im behind a firewall. Im not sure where to configure the proxy to get forge working. I’ve been reading up on configuring the proxy settings for npm but it’s not working.
Att is a screenshot of the error im getting as well as the proxy settings ive set so far
hey everybody
old solution
had to follow the following steps to get this working:
- download and install latest version of npm
- configure proxy entries in the .npmrc file: stackoverflow dot com/questions/7559648/is-there-a-way-to-make-npm-install-the-command-to-work-behind-proxy
- install windows global build tools: github dot com/nodejs/node-gyp#on-windows
- manually install node-gyp: npmjs dot com/package/node-gyp
- NODE_TLS_REJECT_UNAUTHORIZED=0 and rerun forge install: github dot com/nodejs/node-gyp/issues/695
Please refer to my latest comment. The previous solution I posted (although it worked for me) wasn’t very secure.
2 Likes
This doesn’t solve the problem
Hi @HimanshuGupta
We ended up going a bit further. To get Forge to work (without having to compromise security)
- Had to configure node.js for proxy use
- had to configure node.js to utilize our corporate root certificate
Setting up proxy for node.js
you can set the following either as environment variables or in your .npmrc config (i did both)
proxy=http://yourproxyurl:yourproxyport/
http_proxy=http://yourproxyurl:yourproxyport/
https_proxy=http://yourproxyurl:yourproxyport/
noproxy=somesitethatdoesntneedproxy
Setting up your root cert in node.js
you can set the following either as environment variables or in your .npmrc config (i did both)
NODE_EXTRA_CA_CERTS =“path of your pemfile”
You’ll need to convert your rootcert from CRT to PEM to use it in NodeJS.
You want to consider putting these changes in both locations (nodejs config and environment vars) since different ide’s will use different sources for their information