Skip to content
This repository has been archived by the owner on Oct 24, 2018. It is now read-only.

Downloading from HTTPS mirrors always returns "Failed to create SSL context" #112

Closed
Rainmaker52 opened this issue Mar 28, 2016 · 14 comments

Comments

@Rainmaker52
Copy link

When using pamac-updater, downloading packages from HTTPS enabled mirrors always returns "Failed to create SSL context".

Using yaourt from the command line works fine.

I've tried several different mirrors. The SSL certificate of the site is valid, within validity range and signed by public CA.

@guinux
Copy link
Contributor

guinux commented Mar 29, 2016

Can you give me the mirror url, I will see this.

@philmmanjaro
Copy link
Member

Normally we just use the HTTP URLs. Ssl URLs we have to check.

@Rainmaker52
Copy link
Author

I use
https://mirror.i3d.net/pub/archlinux/$repo/os/$arch

Also tried:
Server = https://arch.32g.eu/$repo/os/$arch
Server = https://mirror.compojoom.com/archlinux/$repo/os/$arch
Server = https://archlinux.cyborg-connect.de/$repo/os/$arch
Server = https://mirror.f4st.host/archlinux/$repo/os/$arch

And some others :)

I use SSL mirrors because my laptop is quite often behind a guest wifi network. Login pages and stuff, corrupt the pacman database.

That bug was reported as https://bugs.archlinux.org/task/46107?opened=21341&type%5B0%5D=&sev%5B0%5D=&due%5B0%5D=&cat%5B0%5D=&status%5B0%5D=open&percent%5B0%5D=&reported%5B0%5D= , in case anyone is interested.

@guinux
Copy link
Contributor

guinux commented Mar 31, 2016

As you are using Archlinux, it's maybe because openssl was updated, can you try to rebuild pamac ?

@Rainmaker52
Copy link
Author

For a reason beyond my comprehension, rebuilding actually worked.

I don't really understand why I should recompile when a shared library gets updated. Before rebuild, the program already seemed to be correctly linked :
~ ldd which pamac-updater | grep ssl
libssl.so.1.0.0 => /usr/lib/libssl.so.1.0.0 (0x00007f69459d2000)

But, it worked. Thanks.

@Rainmaker52
Copy link
Author

This may require an extra look.
Without changing or upgrading anything, the error is back (?).

Exact error is:
Error: failed retrieving file 'multilib.db' from ftp.fau.de : SSL: couldn't create a context: error:140A90F1:lib(20):func(169):reason(241)

Could someone try to reproduce?

@Rainmaker52 Rainmaker52 reopened this Apr 2, 2016
@Strit
Copy link

Strit commented Apr 11, 2016

I also have a similar error when using my own repo, which is on a https site.
Updating with pacman directly is no problem.

Also it only happens with the updater, not the software installer.

EDIT: Just deleted and re-did the repo's databases, and updated one of the files. No error this time.

@seilaeu
Copy link

seilaeu commented Apr 21, 2016

I had this issue in Arch Linux, using secure mirrors, and the solution for me it was the update of my mirrorlist with command 'sudo reflector --verbose -p https -f 30 -l 30 -n 15 --sort rate --save /etc/pacman.d/mirrorlist'.

@ringo32
Copy link

ringo32 commented May 22, 2016

like netcologne of manjaro repo also have a SSL part

@rnfll
Copy link

rnfll commented May 22, 2016

can confirm, that this error is still exists (atleast in pamac 4.0-1)

Im on manjaro, uses self-modified mirrorlist (actually, some of manjaro mirrors can in https).
Tried to update with pamac today - got packages list without problems, but, on upgrade, this error happened:

SSL: couldn't create a context: error:140A90F1:lib(20):func(169):reason(241)

Tru pacman, everything went fine

@guinux
Copy link
Contributor

guinux commented Aug 6, 2016

I tried to fix SSL support in my last commit, please try and report.

@rasisin
Copy link

rasisin commented Aug 18, 2016

I'm getting the same error messages when doing normal updates of Manjaro. I work outside the IT field so my system has a default Manjaro setup. The update seems to happen successfully, but I think the problem slows down the update--the updater (pacman?) looks like it's searching through a long list of mirrors for each update.

@philmmanjaro
Copy link
Member

Did you test the pamac-dev 4.1.1-2 package yet, which includes that fix. Should be now available on all branches.

@rasisin
Copy link

rasisin commented Aug 26, 2016

Thank you! I installed the package, and now the error messages are gone.

@guinux guinux closed this as completed Aug 26, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants