update failed more than 50 times: SSL Certificate is invalid #966
Comments
Well, it's like you said, the ssl cert is invalid which could also mean that your certs are out of date. Nothing I can do here |
Could also be some sort of MITM. |
Your distro? |
Btw, here's the cases when this can happen:
|
My site is hosted on FreeBSD 10.3. No issue with my certs, as far as I know. Check yourself: https://cbrace.nl |
Here's the explanations: https://curl.haxx.se/libcurl/c/libcurl-errors.html |
Ok, created a PR to get the curl error code: https://github.com/fguillot/picoFeed/pull/263/files which will let us debug this issue in a better fashion. |
BTW, my first guess would be that your FreeBSD PHP/openssl package does not support the required SSL ciphers. |
I'm now seeing this: Just as a test: |
It doesn't seem to a permissions thing:
|
No idea how to solve this on freebsd |
Hold on, I think this IS a permissions thing. `colin@galatea ~ $ ls -l /usr/local/share/certs/ca-root-nss.crt colin@galatea ~ $ sudo chmod 644 /usr/local/share/certs/ca-root-nss.crt colin@galatea ~ $ ls -l /usr/local/share/certs/ca-root-nss.crt -rw-r--r-- 1 root wheel 900648 Mar 4 18:32 /usr/local/share/certs/ca-root-nss.crt` `$ curl -l https://gianalytics.org/xfeed/ ... OK, now I can add that feed in News. Refreshed News. Good, now all the orange bands are gone. I think this is a packaging error recently introduced in** ports/ca_root_nss** and I will take it up with the FreeBSD ports packager. Many thanks for your help. |
Ok, great that this could be fixed :) |
I'm asking about this here: https://forums.freebsd.org/threads/55804/ |
Will post a follow up, if possible. |
Hello,
A number of the feeds I have subscribed to are now banded in orange and the mouseover displays the error message above. As a result, they are no longer updated. Among the feeds affected are various hosted by Google and owncloud.org itself (see attached screencap). Please let me know what additional information I can supply to help solve this issue.
System Information
The text was updated successfully, but these errors were encountered: