• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support Troubleshooting Networking & Access SOLVED: Connection problem after SSL certificate update

     
    • 0 Vote(s) - 0 Average

    SOLVED: Connection problem after SSL certificate update

    applies only to the use of TV apps
    Burkhazad
    Offline

    Junior Member

    Posts: 21
    Threads: 3
    Joined: 2023 Dec
    Reputation: 0
    Country:Germany
    #1
    2026-05-07, 11:58 PM (This post was last modified: 2026-05-08, 12:13 AM by Burkhazad. Edited 1 time in total.)
    Hello everyone,

    Here’s the situation:
    Jellyfin is installed on a Windows Server. IIS is set up as a reverse proxy with the APP and URL Rewrite, and I’m using an SSL certificate from IONOS.

    Everything had been working fine until now, but I had to renew my SSL certificate in early May.
    Now I’m facing the problem that everything works (mobile app—Xiaomi, Chrome, Firefox, etc.), but on the Fire TV Stick and the TV box (MagentaTV One), I can no longer establish a connection.

    The only message I get is “No access.”

    Otherwise, nothing has changed. On the IIS, I installed the new certificate via PFX and password and also selected the corresponding certificate again in the bindings. This certificate is from IONOS and issued by Sectigo.
    SSL Checker says everything is fine. I also loosened the SSL connection settings a bit, but unfortunately that didn’t help.

    On the FireTV and the corresponding Jellyfin app, I also cleared the cache and data and tried a reinstallation. Unfortunately, none of this helped.

    Does anyone here have any tips? DDNS is working properly; as before, only port 443 is forwarded in the router. As I said, I didn’t change any of the settings myself—I just renewed the certificate.

    So I’d really appreciate your help, since all my experiments—including using intermediate certificates, etc.—have been unsuccessful. Unfortunately, it doesn’t work even when I integrate it directly through Jellyfin.



       
    Go to solution
    Burkhazad
    Offline

    Junior Member

    Posts: 21
    Threads: 3
    Joined: 2023 Dec
    Reputation: 0
    Country:Germany
    #2
    2026-05-08, 07:17 PM
    I was able to solve my problem on my own today, and I thought I’d share a quick tip in case others are experiencing the same issue.

    It has nothing to do with Jellyfin!
    There was some confusion with the SSL certificate and the certificate path. The intermediate certificates weren’t transferred correctly.

    Thanks to Google AI, which directed me to whynopadlock.com, and the use of DR-NetTools on the TV, I was able to narrow down the problem and, with the help of the AI, clean up and correct the Windows certificate store.

    Now everything is working as it should again.

    Translated with DeepL.com (free version)
    1
    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode