+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Guides, Walkthroughs & Tutorials (https://forum.jellyfin.org/f-guides-walkthroughs-tutorials)
+--- Thread: Jellyfin for Kodi, Reverse Proxy, and Custom Certificate Authority (/t-jellyfin-for-kodi-reverse-proxy-and-custom-certificate-authority)
Jellyfin for Kodi, Reverse Proxy, and Custom Certificate Authority - Sea Monkey - 2025-10-25
I spent a lot of time figuring this out, and am hoping this might be useful to others with a similar configuration.
I have my Jellyfin server bound to 127.0.0.1 sitting behind a reverse proxy running on Apache using a certificate generated by my own certificate authority on pfSense. Adding my certificate authority to the system-wide and Firefox trust stores was sufficient to get access via browser and the official JMP client working, but not Jellyfin for Kodi.
In the Jellyfin dashboard under Advanced:Networking, make sure you have your hostname.localdomain in 'Known proxies' and all=https://hostname.localdomain under 'Published Server URIs'.
In Linux, appending the contents of my CA.pem to ~/.kodi/addons/script.module.certifi/lib/certifi/cacert.pem was sufficient to get HTTPS working. In Windows, you will also have to append the contents of your custom CA.pem to C:\Program Files\Kodi\system\certs\cacert.pem. Obviously, this won't survive updates to these files, but these shouldn't change very frequently. If you have an existing Jellyfin for Kodi configuration that doesn't already use https://hostname.localdomain, you'll have to uninstall/reinstall Jellyfin for Kodi and fully purge the settings. You might want to even delete the jellyfin, MyMusic, MyVideos, and TV db files in userdata/Database prior to starting Kodi and re-adding Jellyfin for Kodi just to be absolutely sure you are starting with a clean configuration. I think that particular step was only necessary on one of my Windows instances to get it unstuck.
Hope this helps!