beg1294 0 Posted December 2, 2021 Posted December 2, 2021 Hi there, I almost did everything to fix the problem but no luck. Whenever I try to connect over https (public or local) doesn't matter, it keeps refusing. Everything started with outdated SSL, so I renewed with LetsEncrypt and replaced, it worked like a charm like 1-2 days, and things started to happen. I even recreated SSL certificate but still no luck. Guys could help me somehow becaus I am out of ideas. Here tech specs: OS: Ubuntu 20.04 Logs: Attached Any help is appreciated. Thank you in advance embyserver-63774053882.txt embyserver-63774054209.txt embyserver-63774054790.txt embyserver.txt
Luke 42079 Posted December 2, 2021 Posted December 2, 2021 Hi, did you restart emby server after doing that?
beg1294 0 Posted December 2, 2021 Author Posted December 2, 2021 Yeap, I restarted even the server itself
Solution Q-Droid 989 Posted December 2, 2021 Solution Posted December 2, 2021 The Emby server is having trouble with your cert store. If it can't open the file it won't bind on the HTTPS port. 2021-12-02 15:13:10.515 Error App: Error loading cert from /home/user/Documents/ssl/video.lexx.cloud.pfx Make sure the Emby runtime process user (usually emby) can access the full path to that file. This is one of the reasons why I usually recommend to copy/move the cert store to somewhere in the emby config path, like /var/lib/emby/ssl (or /config/ssl for docker) and make sure the directory and file are owned by emby:emby.
Luke 42079 Posted December 3, 2021 Posted December 3, 2021 Ah yes I missed that. Judging from the error it may not have read access to that file path.
beg1294 0 Posted December 3, 2021 Author Posted December 3, 2021 (edited) 12 hours ago, Q-Droid said: The Emby server is having trouble with your cert store. If it can't open the file it won't bind on the HTTPS port. 2021-12-02 15:13:10.515 Error App: Error loading cert from /home/user/Documents/ssl/video.lexx.cloud.pfx Make sure the Emby runtime process user (usually emby) can access the full path to that file. This is one of the reasons why I usually recommend to copy/move the cert store to somewhere in the emby config path, like /var/lib/emby/ssl (or /config/ssl for docker) and make sure the directory and file are owned by emby:emby. God, thank you, you made my day. It worked like a charm, the only thing I did, changed owner to emby user Edited December 3, 2021 by beg1294
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