2024-02-28, 06:53 PM
I "solved" this problem, but what I did should not have made any difference, and any quick google search shows that these same symptoms show up for many, many people with the app.
I'd like to keep troubleshooting to help understand WHY this issue occurs.
Original situation:
https is enabled, http does not work for certain clients.
Disable https, http still doesn't work for certain clients.
What "fixed" it:
disable https. completely restart jellyfin.service.
connect problem clients on http. (no ssl). It works this time! (for me, on two devices)
re-enable https. completely restart jellyfin.service.
Now the devices which previously could not connect with http, can connect with http.
Devices already using https may continue using https.
Enabling https without requiring https should not affect http connections.
<EnableHttps>true</EnableHttps>
<RequireHttps>false</RequireHttps>
Ideally, all devices could use https, but if that's not the scope of the jellyfin app (reverse proxy and all that) I understand.
As for your question Dread, I do not know certs well enough to answer that, which is why I was so willing to just turn off https for troubleshooting.
I use pfsense as my trusted CA, and generate a server cert. I then download that p12 and use it for the jellyfin server.
For some android apps and ALL browsers, this is sufficient.
Inside the chain.pem, I have 2 "cert" sections, so
-----BEGIN CERTIFICATE-----
jhkdsjakhdskjhdgjhsgjkhfdsajhk
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
jhfdajhkfdsfdskjhlfdsjhkfdsjkhjhfdsak
-----END CERTIFICATE-----
the .pem has only one such section.
I'd like to keep troubleshooting to help understand WHY this issue occurs.
Original situation:
https is enabled, http does not work for certain clients.
Disable https, http still doesn't work for certain clients.
What "fixed" it:
disable https. completely restart jellyfin.service.
connect problem clients on http. (no ssl). It works this time! (for me, on two devices)
re-enable https. completely restart jellyfin.service.
Now the devices which previously could not connect with http, can connect with http.
Devices already using https may continue using https.
Enabling https without requiring https should not affect http connections.
<EnableHttps>true</EnableHttps>
<RequireHttps>false</RequireHttps>
Ideally, all devices could use https, but if that's not the scope of the jellyfin app (reverse proxy and all that) I understand.
As for your question Dread, I do not know certs well enough to answer that, which is why I was so willing to just turn off https for troubleshooting.
I use pfsense as my trusted CA, and generate a server cert. I then download that p12 and use it for the jellyfin server.
For some android apps and ALL browsers, this is sufficient.
Inside the chain.pem, I have 2 "cert" sections, so
-----BEGIN CERTIFICATE-----
jhkdsjakhdskjhdgjhsgjkhfdsajhk
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
jhfdajhkfdsfdskjhlfdsjhkfdsjkhjhfdsak
-----END CERTIFICATE-----
the .pem has only one such section.