Error after Upgrading to Gleam 1.1.0 -> Invalid Peer Certificate: UknownIssuer

[RNGKing]

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.

[lpil]

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?

[kitoid]

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:

> gleam update
  Resolving versions
error: Dependency resolution failed

An error occurred while determining what dependency packages and
versions should be downloaded.
The error from the version resolver library was:

Unable to determine package versions: error sending request for url
(https://repo.hex.pm/packages/gleeunit): error trying to connect: invalid
peer certificate: UnknownIssuer

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:
https://stackoverflow.com/questions/16668508/how-do-i-configure-git-to-trust-certificates-from-the-windows-certificate-store

Thanks for your help!

[lpil]

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.