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
Jackett frequently fails with OPENSSL_internal:CERTIFICATE_VERIFY_FAILED #7237
Comments
Hmm, from what I can see in the log, it would appear that the problem started after the auto update finished updating from 0.12.1815 to 0.13.127 and the Jackett service was started back up. Then monitor Jackett over the 5 days or so, and see if you get a repeat of the problem as regularly as you used to get. |
Thanks I’ll try that, FWIW when I try manual updates it usually succeeds and when I checked just now it updated to 0.13.135 without issues. |
I can reproduce the issue in Mono build. Manual search for "" on shokweb with 0 results.
|
@garfield69 I've disabled auto updates and Jackett is currently in the bug state:
|
@epheterson Try this (and restart Jackett) => https://www.mono-project.com/docs/about-mono/releases/3.12.0/#cert-sync |
Thanks, I tried the cert-sync command and will keep an eye on it now to see if this resolves it:
|
Unfortunately that didn’t work, it’s still hitting the same errors. |
I can't help you more because it is a Mono issue, not Jackett. You can try to update your system and then execute |
some syno users have had success with the .net core builds from docker https://hub.docker.com/r/linuxserver/jackett/ |
I'm using a Synology and I was getting the same annoying messages... after investigating, I have set a daily task that performs the following (My Nas is set to reboot every day also):
Edit the paths as needed, if you do not reboot the nas you might need to restart jackett using synoservicectl This way I have manage to reduce the times that the issue appears. In those rare cases that it appears (can't remember when was the last time), I just need to re-run those commands and restart Jackett. Hope this helps! |
Environment
OS: Synology DSM 6.2.2-24922 Update 4
.Net Runtime: Mono
.Net Version: 5.18.0.240-12
Jackett Version: 0.13.127.0
Are you using a proxy or VPN? No
Description
Usually Jackett works great, e.g. after a fresh boot, but often it'll go into this state where everything fails. Checking for updates fails, and testing every indexer fails. When in this state I've found no solution other than relaunching Jackett, which always works. The other variants I've seen of this on Github are either permanent, i.e. reproduce after a fresh boot, or affect only one indexer.
Logged Error Messages
jackett.log
jackettRelaunched.log
Example while testing indexer:
The text was updated successfully, but these errors were encountered: