rod626 Posted July 18 Share Posted July 18 Using Synology DSM7, I upgraded from Emby 4.6.* to 4.7.5.0 by doing a manual install of the apk per the usual instructions. After updating, I was unable to connect via SSL, always receiving "connection refused" error in all browsers. The emby logs were no help. I eventually narrowed it down to the fact that the install had deleted my certificate from /var/packages/EmbyServer/target/etc/ssl/certs/. To fix it, I copied the certificate back to that location, then set permissions with chmod 644 and chown emby:emby. Everything else worked fine. Link to comment Share on other sites More sharing options...
Luke Posted July 18 Share Posted July 18 Hi, thanks for following up with the solution ! Link to comment Share on other sites More sharing options...
heffeque Posted July 18 Share Posted July 18 Hopefully this will be fixed in 4.7.6.0 when it comes to the Package Center, correct? Link to comment Share on other sites More sharing options...
rod626 Posted July 18 Author Share Posted July 18 1 hour ago, heffeque said: Hopefully this will be fixed in 4.7.6.0 when it comes to the Package Center, correct? I’m not sure. I use commercial SSL certs and I have emby and DSM using different SSL certs, and bound to different DNS names. I would expect that most people will just use the free certs from letsencrypt, or the cert bound to DSM, so the upgrade will want to get those scenarios correct first. Link to comment Share on other sites More sharing options...
heffeque Posted July 18 Share Posted July 18 Ah, misunderstood your issue then... Using letsencrypt here, in combination with reverse proxy, which seems to work fine. Link to comment Share on other sites More sharing options...
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