mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
TLS/HTTPS support broken #437
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ghost on GitHub (Feb 19, 2019).
Describe the bug
Jellyfin documentation recommends using HTTPS over HTTP, but HTTPS/TLS support is broken, erroring with
ERR_SSL_PROTOCOL_ERRORinChrome Version 74.0.3702.0 (Official Build) dev (64-bit)andSSL_ERROR_RX_RECORD_TOO_LONGinIceCat (Firefox) 60.5.0esr (64-bit).To Reproduce
Expected behavior
Jellyfin should work over HTTPS as the documentation implies/recommends.
Logs
N/A
Screenshots
N/A
System (please complete the following information):
Additional context
N/A
@cvium commented on GitHub (Feb 19, 2019):
Did you generate an SSL certificate?
@ghost commented on GitHub (Feb 19, 2019):
I did not, as I encountered the error during first time setup; the first time setup documentation lists an HTTPS URL, so this may be a simple documentation error rather than a bug if Jellyfin cannot be setup under HTTPS the first time.
@cvium commented on GitHub (Feb 19, 2019):
It's on the roadmap to (re)implement self-signed cert generation and Let's Encrypt (as a plugin).
So yes, you are correct. It seems the documentation is lacking wrt. SSL certificate generation. It cannot be accessible via https without a certificate. I think you can generate a self-signed cert with openssl in Linux:
cc @joshuaboniface
@JustAMan commented on GitHub (Feb 19, 2019):
Also port 8096 is by default plain http, not https. Maybe it's the reason for the issue you're seeing.
@jerome-diver commented on GitHub (Jun 30, 2021):
is there any news about this bug report ? I have the same problem...
@RIS2000 commented on GitHub (Sep 12, 2021):
same for me (
@cvium commented on GitHub (Sep 12, 2021):
The issue is closed
@RIS2000 commented on GitHub (Sep 12, 2021):
what is the fix ?
@RIS2000 commented on GitHub (Oct 1, 2021):
this is helped me on desktop, but no luck on android (
@BigBrawler commented on GitHub (May 2, 2023):
The following fixed this issue for me. Did these with no dice.
Paid for keypair file online via csr service. [x]
Generated using openssl cli. [x]
THE FIX:
openssl pkcs12 -export -out c:\jellyfin.pfx -inkey <path-to-privatekey>\jellyfin-private.key -in <path-to-certificate>\jellyfin-cert.cer -passout pass:@Blarnix commented on GitHub (Jun 23, 2023):
@BigBrawler That was the fix for me. I was using a .p12 certificate before as Jellyfin had said in the networking UI and that wasn't valid as it seemed. Thanks for finding this fix.