samury314 1 Posted August 17, 2024 Posted August 17, 2024 I have a valid SSL certificate from No IP that I converted to .pfx and copied into several locations on my Debian/OMV server via WinSCP and a Samba share, including into/etc/ssl/certs/. When I try to put the location of the file in Custom SSL Certificate Path under Network on the left-hand Settings pane it cannot find it, no matter the location I specify. The directories and files listed when I search from the Custom Certificate Path magnifying glass do not match those in WinSCP or the share either. What is going on? How do I get Emby to recognize my certificate? How do I get the /etc/ssl/certs/ directory in Emby to match the one in my share? Thanks for any help.
Luke 42077 Posted August 18, 2024 Posted August 18, 2024 Hi, one thing you might want to try is putting the certificate file somewhere under the server data folder. This will guarantee that the server has access to that location. Please let us know if this helps. Thanks.
samury314 1 Posted August 18, 2024 Author Posted August 18, 2024 Thanks for the advice, but it is not working so far. It's like the server that Emby sees when I put the location in is completely different from the actual server that is there. Are these hidden in var/lib/docker/? I'm very confused. Emby is installed via Docker on a system with Debian 11 and OMV 6. Emby works fine on my Shield and Roku, but my experience installing the certificate seems to differ from what I've researched.
Q-Droid 989 Posted August 18, 2024 Posted August 18, 2024 @Lukeis suggesting that you place the certificate file in the path that's mapped to /config in the Emby Docker container. Create a directory "ssl" so that you end up with /config/ssl in the container, place the pfx file there and use the /config/ssl/<filename>.pfx in the Emby settings. The second part is that the file must be readable by the Emby runtime process. Preferably the UID/PUID you're using for the Emby container should own the pfx file and be able to access the /config/ssl directory. 1
samury314 1 Posted August 18, 2024 Author Posted August 18, 2024 Thank you both. I finally figured a way to do it with the tips you provided. I used "docker cp [ssl file] CONTAINER:/Emby/config/data" and that copied it to a location I could find from Emby settings.
Luke 42077 Posted August 19, 2024 Posted August 19, 2024 Yea putting it in the data directory is not required, however it seemed like the easiest way to get you squared away.
samury314 1 Posted August 19, 2024 Author Posted August 19, 2024 I was just happy to get it into a directory where Emby could find it. I tried CONTAINER:/Emby first but it still didn't see it there. Config/data did the job though. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now