I can confirm that it's definitely caused by the update and that @rockcavera's solution is what you should use.
However, this assumes that you are on Windows, if you're on Unix I would like to know more details about your operating system.
When installing Nim on Windows, I am in favor of making cacert.pem available in /bin. It would be a way to avoid these mistakes. Also, add some message when compiled with -d:ssl and -d:release or -d:danger to distribute the executable with cacert.pem.
Just a suggestion.
Just a suggestion.
Will be fixed, I thought we were doing that.
I think shipping the cacert.pam next to the two ssl*.dlls and reading it from there is the best option. When user distributes their windows .exe they already have to copy the ssl*.dlls what's an extra cacert.pam file?
It does not look like nim 1.4.4 ships with cacert.pam nor does it read it from the .choosenimtoolchainsnim-1.4.4bin folder like the docs lead me to believe it should.
This way nim programmer do not have to worry about cacert.pam, unless they distribute. When they distribute, they have to know about all of the dlls they need anyways, treat cacert.pam like a "dll" file, just extra thing they need to ship with.
I also would change error message "Exception message: No SSL/TLS CA certificates found." to some thing like "No SSL/TLS CA certificates cacert.pam file found." so its clear what its looking for.
I'm also seeing this issue on Ubuntu 20.04 with Nim 1.4.4, 1.4.6 and 1.4.8. I don't see the issue on 1.4.2.
I'm building my program in a nimlang/nim docker container, then distributing the compiled binary to run on a different Ubuntu 20.04 computer.
The ca-certificates package is installed and up to date on the Ubuntu computer.
What else can I tell you to help diagnose the problem?