Error after Upgrading to Gleam 1.1.0 -> Invalid Peer Certificate: UknownIssuer #3152
Replies: 6 comments 3 replies
-
Hello! We don't have any special support for proxies etc so this is not a bug. What would you need for us to be able to support you? |
Beta Was this translation helpful? Give feedback.
-
Hi Louis! I'm having the same issue as well. Our corporate firewall acts as a transparent proxy and decrypts all traffic for security inspection, replacing the certificate chain with its own root certificates in order to be able to perform decryption. In my environment, I installed gleam using scoop, and when I run any gleam command, I get the following error:
To be fair, I agree this is not a bug, but probably should be considered as a feature request (to be able to ignore certificate errors, or to add the possibility to specify the location of trusted certificates). I was experiencing the same issue with git command, and in git they offer the possibility to use the Windows certificate storage mechanism: Thanks for your help! |
Beta Was this translation helpful? Give feedback.
-
What is it that is required to support your needs here? We currently will not be able to use any Windows specific APIs, but perhaps a cert could be provided in some other way. |
Beta Was this translation helpful? Give feedback.
-
I am interested in this as well. Rebar for example provides an option to override the certificate path using the 'ssl_cacerts_path' config. Would be very useful to have an option to either override the certificate path. |
Beta Was this translation helpful? Give feedback.
-
This issue is something I'm also directly experiencing. I believe if there's any application with corporate space then this will be important to address. |
Beta Was this translation helpful? Give feedback.
-
In Elixir I was experiencing a similar issue when using mix, when retrieving Hex dependencies. The way I solved it was by using the HEX_CACERTS_PATH environment variable to point to the custom certificate store, or using "mix hex.config cacerts_path /your/certificate/store.pem". See more here: As I was mentioning in a previous comment, that would likely require a "gleam config" command to be added. |
Beta Was this translation helpful? Give feedback.
-
I'm submitting this report from my home computer so there isn't a log I can pull from.
My work computer is a virtual desktop with Windows 10 that routes its connections through a corporate proxy. Installed gleam via Scoop.
When attempting to use "gleam build" after updating from 1.0 the system gave me the error as shown in the title.
I have set the $env:http_proxy and $env:https_proxy in my environment to their correct values, as I'm able to update rust and install various things through the cargo utility.
Beta Was this translation helpful? Give feedback.
All reactions