Open vbskruger opened 2 years ago
A temporary solution is to create a .npmrc file and place it in your home folder (i.e. c:\Users\theUser\.npmrc), with the following content:
https-proxy=http://your.proxy.address.with.port:8080
# If your proxy / firewall does packet inspections and alters the certificates, you can add your custom certificate authority here
ca[]="-----BEGIN CERTIFICATE-----\ntheCertificateInBase64With\n-----END CERTIFICATE-----"
ca[]="-----BEGIN CERTIFICATE-----\nYouCanUseMultipleCA\n-----END CERTIFICATE-----"
Form more info about the .npmrc, you can check here: https://docs.npmjs.com/cli/v7/using-npm/config#https-proxy https://docs.npmjs.com/cli/v7/using-npm/config#ca
You can also just delete the C:/Users/user/AppData/Local/Programs/kontena-lens/resources/extensions/example-extension
folder as it is not necessary. This is probably causing the initial issue as it should be the only bundled extension that actually has any run-time dependencies.
Describe the bug Lens uses npm to load the dependencies of the default extensions (i.e. pod-menu). However, if you are behind a company proxy, and you define the proxy settings in the preferences --> proxy page, it seems npm ignores it, leading to a timeout in the connection and not installing the dependencies.
To Reproduce Steps to reproduce the behavior:
Expected behavior Lens should load the dependencies of the extensions using the defined proxy settings.
Environment (please complete the following information):
Logs: