-
-
Notifications
You must be signed in to change notification settings - Fork 104
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
Custom CA cert self signed SSL certificate not supported #358
Comments
Not sure why it's not trusting the cert if your OS trusts the cert. As a workaround till we can look into the code causing this issue you can disable ssl verification in the settings of the addon. That should allow you to connect to jellyfin with your self signed cert |
Yes, I'm currently trying to disable the check with the "Verify connection" toggle in the settings. |
Hmmm doesn't seem to work, I still have CERTIFICATE_VERIFY_FAILED errors even with |
Here is another log after I changed the URL to the SSL endpoint with sslverify=false Addtional info that I didn't mention in the ticket is : I'm running Kodi in portable mode with the "-p" switch |
The Nope got better. needs to be |
Still an issue, please reopen.
Because jellyfin-kodi relies on root certs profided by certifi: Please remove the dependency on certifi. Instead, the jellyfin add-on must either
|
In a word, no. At this point, it's not an issue, it's a feature request we have no interest in encouraging. We use the requests library for our network code. requests depends on certifi. And there's no way we're rewriting all of our network code for the half a dozen people out there who want this. If you want to use a self signed cert, you can disable verification. |
OK, thanks for quick reply. I did not know it would be so difficult to get rid of certifi. |
Describe the bug
Cannot add a server which is on an SSL endpoint with a self signed certificate
To Reproduce
Expected behavior
The jellyfin add-on must either
Adding a self signed SSL server must work
Logs
System (please complete the following information):
The text was updated successfully, but these errors were encountered: