JKS been around for decades and only now folks started to care it is proprietary. It's not more or less secure, just a warning. ![]() Until Sindre updates the Subsonic code to use PKCS12 instead of JKS, we can't convert this either. This is just a warning, you can safely ignore it. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore subsonic.keystore -destkeystore subsonic.keystore -deststoretype pkcs12". The JKS keystore uses a proprietary format. I also get a warning after the keytool command: Keytool -list -storepass subsonic -keystore subsonic.keystore and see if the Let's Encrypt certificate is there. Unzip /usr/share/subsonic/subsonic-booter-jar-with-dependencies.jar subsonic.keystore If they are there, then are there any error messages on Subsonic's logs? Perhaps you should extract subsonic.keystore and review its contents: ![]() If they are not there, then you need to review the steps. Zipinfo /usr/share/subsonic/subsonic-booter-jar-with-dependencies.jar it should be listed there, and with the correct date of when you updated with with the Let's Encrypt files. I followed these instructions, but am still getting the subsonic certificate instead of the letsencrypt one.Ĭheck if the Java keystore subsonic.keystore file made it into the Subsonic jar file:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |