-
Notifications
You must be signed in to change notification settings - Fork 486
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
Pacman- SSL certificate problem. #2529
Comments
Solved: |
In my setup, those are already in that path. |
I copied the cert to the according folder but I still get the cert error. |
Is it not required to copy certificates manually. Try to update the packages with |
and what about those of us behind corporate proxies/firewalls that have their own SSL certificates/perform MITM? need a way to ignore SSL errors |
The procedure is explained here https://www.msys2.org/docs/faq/ |
Most of them still face this issue even with the above solution, if you are also one among them then try this. Solution: Note: please click on the highlighted hierarchy while downloading the cert file. |
Describe the issue
SSL certificate problem.
Steps to Reproduce the Problem
When I execute "pacman -Syu", it shows alot of errors related to SSL certificate problem. How can I solve this issue?
:: Synchronizing package databases...
error: failed retrieving file 'mingw32.db' from repo.msys2.org : SSL certificate problem: self signed certificate in certificate chain
error: failed retrieving file 'mingw32.db' from downloads.sourceforge.net : SSL certificate problem: self signed certificate in certificate chain
error: failed retrieving file 'mingw32.db' from www2.futureware.at : SSL certificate problem: self signed certificate in certificate chain
error: failed retrieving file 'mingw32.db' from mirror.yandex.ru : SSL certificate problem: self signed certificate in certificate chain
error: failed retrieving file 'mingw32.db' from mirrors.tuna.tsinghua.edu.cn : SSL certificate problem: self signed certificate in certificate chain
The text was updated successfully, but these errors were encountered: