Что такое problem with the ssl ca cert path access rights
Обновлено: 05.07.2024
This is an issue with ca-certificates that bundles with the server. You may simply need to reinstall the following packages for fixing this issue.
This will fix your issues, with curl: (77) Problem with the SSL CA cert (path? access rights?)
See Also:
Popular Category
About the author
Syslint ™ Technologies is a technical support and software development company offering enterprise solutions since 2008. Our team consists of people that have been mastering their knowledge about all sorts of Unix / Linux systems. With such experience, we joined the web hosting industry in order to make your business grow faster and smoother. Our system administration and security services have been appreciated by many companies throughout the world that run their businesses on Unix platform.
Conclusion
In short, the curl error 77 problem with the SSL CA cert occurs when SSL chain certificate files are missing or broken. Today, we saw how our Support Engineers fixed this error.
Related posts:
PREVENT YOUR SERVER FROM CRASHING!
Never again lose customers to poor server speed! Let us help you.
Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.
What is curl error 77 problem with the SSL CA cert?
Curl error 77 error is a server-side error. This error indicated that the chain certificate files are missing or “broken”. Usually, this error happens simply by outdated SSL certificate(s) for cURL installed on the server. Also, the wrong or incomplete configuration settings on the server can trigger the error on the website.
The error looks like,
This error occurs when PHP cURL uses an outdated set of root certificates to verify server certificates.
PHP Problem with the SSL CA cert (path? access rights?)
Had this happen to two servers which use the PayPal IPN, both at around the same time.
Fix was to restart Apache.
Had it happen too. An automatic update had happened, which created a new /etc/pki/nssdb/pkcs11.txt (and moved the old one to /etc/pki/nssdb/pkcs11.txt.rpmnew). File contents were the same. There were no warnings or other information in the logs. I have no idea if the automatic update was the culprit though. Anyhow, a restart of php-fpm did solve the issue. For those who use nginx + php-fpm on CentOS: sudo service php-fpm restart should do the trick I can confirm that this helped me as well. After going up and down trying to find why cURL in PHP would work on the CLI but not in Apache, a simple Apache restart fixed the issue. RHEL 6.5. Was this successful for anyone running a Jetty server?If you are getting "Problem with the SSL CA cert (path? access rights?)" it may very well mean that you have either deleted everything from /etc/pki/tls/certs/ or have set invalid permissions (CHMOD).
If you are using RHEL/CentOS, try yum reinstall openssl ca-certificates -y
58.3k 65 65 gold badges 245 245 silver badges 389 389 bronze badgesJust upgraded to PHP 5.5.17 and this is when the trouble started. The server runs PayPal transactions and cURL started failing on this error: "Problem with the SSL CA cert (path? access rights?)".
I tried regenerating the certs, modifying the curl options, nothing was getting me anywhere. The solution was to simply reboot the server (CentOS 6.5 in my case). Hope this helps someone.
3,406 2 2 gold badges 23 23 silver badges 42 42 bronze badges I concur; rebooting the server fixed the problem for me also :)It happen to me after update of packages.
Once I restarted the apache it got fixed.
Then I installed it at production server and I got it again. This time it was mess at the certificates under /etc/pki/tls/certs/
PHP Problem with the SSL CA cert (path? access rights?)
Had this happen to two servers which use the PayPal IPN, both at around the same time.
Fix was to restart Apache.
Had it happen too. An automatic update had happened, which created a new /etc/pki/nssdb/pkcs11.txt (and moved the old one to /etc/pki/nssdb/pkcs11.txt.rpmnew). File contents were the same. There were no warnings or other information in the logs. I have no idea if the automatic update was the culprit though. Anyhow, a restart of php-fpm did solve the issue. For those who use nginx + php-fpm on CentOS: sudo service php-fpm restart should do the trick I can confirm that this helped me as well. After going up and down trying to find why cURL in PHP would work on the CLI but not in Apache, a simple Apache restart fixed the issue. RHEL 6.5. Was this successful for anyone running a Jetty server?If you are getting "Problem with the SSL CA cert (path? access rights?)" it may very well mean that you have either deleted everything from /etc/pki/tls/certs/ or have set invalid permissions (CHMOD).
If you are using RHEL/CentOS, try yum reinstall openssl ca-certificates -y
58.3k 65 65 gold badges 245 245 silver badges 389 389 bronze badgesJust upgraded to PHP 5.5.17 and this is when the trouble started. The server runs PayPal transactions and cURL started failing on this error: "Problem with the SSL CA cert (path? access rights?)".
I tried regenerating the certs, modifying the curl options, nothing was getting me anywhere. The solution was to simply reboot the server (CentOS 6.5 in my case). Hope this helps someone.
3,406 2 2 gold badges 23 23 silver badges 42 42 bronze badges I concur; rebooting the server fixed the problem for me also :)It happen to me after update of packages.
Once I restarted the apache it got fixed.
Then I installed it at production server and I got it again. This time it was mess at the certificates under /etc/pki/tls/certs/
One of the main reasons for this error is broken or missing SSL chain certificate files on the server.
At Bobcares, we help our customers to fix similar SSL errors as part of our Server Management Services.
Today, let’s discuss the details on how to fix this error.
How to fix curl error 77 problem with the SSL CA cert
Curling an SSL website can result in an error curl: (77) Problem with the SSL CA cert (path? access rights?) on certain servers.
This error is the result of SSL chain certificate files in the PKI directory being corrupted or missed.
Therefore, we make sure the files /etc/pki/tls/certs/ca-bundle.crt and /etc/pki/tls/certs/ca-bundle.trust.crt exist on the server. If they do not exist, we set up them for our customers.
Sometimes, the error gets resolve by removing and reinstalling the ca certificate.
In a CentOS server, we use the below commands to remove ca-bundle and to install a ca-certificate.
In Plesk servers, adding the following code to %plesk_dir%admin\conf\panel.ini solve the error. By default,
%plesk_dir% is C:\Program Files (x86)\Plesk\
[Need assistance to fix curl error 77?- We’re available 24/7.]
4 Replies to “curl: (77) Problem with the SSL CA cert (path? access rights?) (SOLVED)”
Читайте также: