How to use nRF Connect v2.0 behind corporate SSL proxy?

[Zoltan Mayer]

Hi, Congratulations on releasing nRF Connect v2.0!
Unfortunately, I'm having trouble with adding apps behind corporate SSL proxy. Is there a workaround for this? Please consider adding feature for proxy configuration and adding trusted root CA certificates. Best regards, Zoltan

yarn-error.log

nrf_conn_err_msg.png

==============================================

UPDATE:

After some trial and error I found the correct configuration for Yarn. Some comments:

• If you don't have Yarn installed, the .yarnrc file needs to be created manually and Yarn seems to require a certain file format (extra blank lines);
• Depending on your SSL proxy, multiple cafile entries may be necessary;
• The certificate file should have base-64 encoded X.509 format;
• If you need to specify the domain in your proxy credentials, url-encode the separating backslash with %5C.

Config example for Windows:

.yarnrc

[Magne Rodem]

Hi,

The installation of apps is handled by Yarn internally in nRF Connect. You should be able to specify proxy and SSL configuration for Yarn in C:\User\<username>\.yarnrc (Windows) or $HOME/.yarnrc (Linux/macOS).

You could try adding proxy settings in .yarnrc:

proxy "http://<proxy-host>:<proxy-port>"
https-proxy "http://<proxy-host>:<proxy-port>"

Or if you need to add trusted CA certificates, add:

cafile "C:\path\to\ca-file.pem"

Alternatively, if you are still having issues, you could add this to .yarnrc to temporarily disable the strict SSL verification to see if it makes any difference:

strict-ssl false

[Zoltan Mayer]

Hi Magne, Thank you for your help.