-
-
Notifications
You must be signed in to change notification settings - Fork 345
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSL Error on Arch #2278
Comments
Rather than embedding the newer command in the error message, I'm thinking we might want to write up a generic wiki covering this topic for all distros, and then link that instead. That way if the command changes again, we could update the wiki instead of the code (and it would consolidate the currently disparate and redundant distro-specific wiki pages on the topic). And of course "If you're on Linux" shouldn't be necessary because CKAN believes it knows your OS in other places. As for why it doesn't work on your system, that might require a Mono expert or an Arch expert to determine. But if it was my system, I would wonder whether there were any other files under |
OK, all the various wiki sections about this are now merged here, along with an explanation of why the errors happen: Created #2279 to replace the reference to |
I looked into the issue and stumbled upon this Wiki Entry, which linked to the ca-certificates package and stated, that this package manage the root ca-storage. I took a look at the source files and took a look at update-ca-trust, more specifically
Therefore the certs should all be in |
This Issue is not resolved. |
Do you by any chance have a proxy server? |
No proxy Server at all. |
Just tried it again with the The error still exists. But the mono version is still the same. Here the full log:
I can curl the To make sure, that this is not some kind of an issue with the wrong source of the trust-storage for the CA Certificates. I cleared the trust-storage in mono and only imported the certificate with |
Yeah, I wouldn't expect any recent changes to affect this. As far as I know, we haven't done anything with certificates since #2297. |
There was hope, some time to spare and the additional try to fix it, by just importing the responsible CA-Certificate into the mono trust-storage. Unfortunately, without a fix. And there still is hope, that the updated information may help someone to fix this issue. |
I'm experiencing this issue on Ubuntu as well. It seems to affect many Linux platforms. The easiest solution is to just require Windows users to install .Net 4.6 or later like they should. Honestly we shouldn't be relying on the TLS 1.2 code in .Net 4.5 that Microsoft found of questionable reliability. |
I am having this problem also on Ubuntu 17.10
|
Same issue on 18.10. |
I just retried it... It just seem to work... I can download the List and install the mods I want to. It's strange, but I'm happy!
|
Background
I seem to be having the same problem as this issue here :
#2253
I tried following directions from there and ran
cert-sync /etc/ssl/certs/ca-certificates.crt
CKAN Version: Installed CKAN from the AUR Repository, its version 1.22.6+e8e10ae2e98e
KSP Version: 1.3.1.1891
Operating System: Arch Linux with 4.15.1-2-ARCH kernel
MONO Version:
Wine Version:
Have you made any manual changes to your GameData folder (i.e., not via CKAN)? Nope
Problem
What steps did you take in CKAN? First I ran the
mozroots --import --ask-remove
command as user and root to get my certificate storage straight. With no success. After that I read about the newcert-sync
process for mono, and ran that as sudo and user, but with no sucess either. On their imports however, they added a whole bunch of new certs to my system storages.What did you expect to happen? Start without any issue and run CKAN correctly
What happened instead? Here is a full trace of a normal start.
Side-Note Change the Error from telling the user to run
mozroots --import --ask-remove
to run thecert-sync
process with the location to be determined to their specific system.The text was updated successfully, but these errors were encountered: