You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 20, 2023. It is now read-only.
I.e. how to create the pkcs12 file that goes into the network.xml<CertificatePath> config item.
I have tried openssl pkcs12 -export -password pass:foo -out certificate.pfx -inkey privkey.pem -in fullchain.pem and the resultingn .pfx file works on Chrome on Linux desktop but is considered insecure by Chrome on Android.
The text was updated successfully, but these errors were encountered:
Indeed, [re-]moving the *.pfx files in /var/lib/jellyfin/.dotnet/corefx/cryptography/x509stores/ca/ did resolve the problem and the above openssl command creates a working certifcate.
Still, adding the above instructions to that doc page would be useful. In the meanwhile I will go open a ticket about the above .pfx caching.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It would be great if https://github.com/jellyfin/jellyfin-docs/blob/master/general/networking/letsencrypt.md had instructions for generating the pkcs12 certificate that Jellyfin needs when not using any kinds of reverse proxies.
I.e. how to create the pkcs12 file that goes into the
network.xml
<CertificatePath>
config item.I have tried
openssl pkcs12 -export -password pass:foo -out certificate.pfx -inkey privkey.pem -in fullchain.pem
and the resultingn.pfx
file works on Chrome on Linux desktop but is considered insecure by Chrome on Android.The text was updated successfully, but these errors were encountered: