You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
HebaruSan
changed the title
[Bug]: Unable to download. Ssl error:0900006e:PEM routines:OPENSSL_internal:NO_START_LINE
Certificate errors on Debian (Ssl error:0900006e:PEM routines:OPENSSL_internal:NO_START_LINE)
Dec 28, 2023
Hi @bladela, thanks for the report. You've already seen this link on the forum, but in case any other Debian users land here, this wiki collects everything we know about cert errors on Linux:
I don't have a Debian system for testing, so I won't be able to investigate this for you. (But I do have an Ubuntu partition, Ubuntu VM, WSL, local Ubuntu Docker containers, and Ubuntu Docker containers on GitHub and AWS, all of which have been running CKAN without problems for a long time, so I'm satisfied that this problem isn't due to something CKAN is doing.) If any Debian users figure out this problem, please reply and consider updating the wiki with your discoveries. Thanks!
Having read more closely, this recommendation from the release notes would at least be useful to try:
We highly recommend that Mac and Linux users upgrade to the latest stable release of Mono from mono-project.com. You will need the equivalent of the mono-complete package for your OS.
Following that recommendation would give you Mono 6.12 instead of 6.8.
Is there an existing issue for this?
Operating System
Debian Linux
CKAN Version
1.34.2
Games
KSP 1
Game Version
1.12.5.3190
Did you make any manual changes to your game folder (i.e., not via CKAN)?
No response
Describe the bug
Linux debian 6.5.0-5-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.5.13-1 (2023-11-29) x86_64 GNU/Linux
ckan is unable to sync the repository and fails with the error as in the object
i've already tried the wiki https://github.com/KSP-CKAN/CKAN/wiki/SSL-certificate-errors, with no results
Steps to reproduce
open ckan
wait for the sync that immediately fails
Relevant log output
The text was updated successfully, but these errors were encountered: