Cant connect when jellyfin is running on https not on port 8096

[cwirz]

Describe the error
When attempting to connect Ombi to Jellyfin using HTTPS with port 443 (instead of the default 8096), the connection fails. The documentation doesn't clearly explain how to configure the hostname/port when Jellyfin is accessed via HTTPS through a reverse proxy.

Location
https://docs.ombi.app/settings/jellyfin/

Specifically in the "Fields" section where it describes:

• "Hostname / IP" field
• "Port" field
• "SSL" field

Suggested correction
The documentation should clarify how to configure the connection when Jellyfin is behind a reverse proxy with SSL termination. Specifically:

1. In the "SSL" field description, it currently states:

   • "If you have enabled SSL in Jellyfin, then turn this on."
   • "If SSL is handled by a reverse proxy, leave it off."

   However, it doesn't explain what hostname/port combination to use when SSL is handled by a reverse proxy.

2. Add clearer examples for common scenarios:

   Scenario 1: Direct Jellyfin connection (no reverse proxy)

   • Hostname: 192.168.1.100
   • Port: 8096
   • SSL: Off

   Scenario 2: Jellyfin with built-in SSL

   • Hostname: 192.168.1.100
   • Port: 8096
   • SSL: On

   Scenario 3: Jellyfin behind reverse proxy (SSL termination)

   • Hostname: jellyfin (internal service name) OR 192.168.1.100
   • Port: 8096
   • SSL: Off
   • Note: Use internal connection, not external HTTPS URL

   Scenario 4: Connecting to external HTTPS endpoint

   • Hostname: jellyfin.example.com
   • Port: 443
   • SSL: On
   • Clarify if this is supported or if internal connection is required

3. Clarify whether Ombi needs to connect to:

   • The internal Jellyfin instance (container name/internal IP)
   • The external HTTPS URL
   • Or if both methods are supported

Screenshots
N/A

Method of access:

• OS: Macos
• Browser: Arc

Additional context
This issue commonly occurs when Jellyfin is deployed behind a reverse proxy (like Traefik, Nginx, or Caddy) that handles SSL termination. Users naturally try to use the external HTTPS URL with port 443 and SSL enabled, but this may not be the correct configuration.

In containerized deployments (Docker/Docker Compose), it's unclear whether Ombi should connect using:

• Internal service names (e.g., jellyfin:8096 with SSL off)
• External domains (e.g., jellyfin.example.com:443 with SSL on)

The current documentation doesn't address this common deployment scenario adequately.

[Berserkir-Wolf]

Ombi should use the internal service name for this, to allow for the best responsiveness from Jellyfin. I'll do a little testing with a Jellyfin deployment at home, see if I can make it work with SSL via a reverse proxy in full.
From memory, some of the Jellyfin API did not play nicely via a reverse proxy when the guide for it was written - that may have changed in newer versions.