Harblar 29 Posted February 14, 2016 Share Posted February 14, 2016 So I've finally got Emby server up and running correctly on my unRAID server, but I've noticed that if I update Emby I have to completely reboot the unRAID server to access it. The Web UI for Emby refuses to load, yet after a complete reboot it works fine. Is this a bug or is there a setting/procedure somewhere that I'm missing? Link to comment Share on other sites More sharing options...
hurricanehrndz 149 Posted February 17, 2016 Share Posted February 17, 2016 (edited) So I've finally got Emby server up and running correctly on my unRAID server, but I've noticed that if I update Emby I have to completely reboot the unRAID server to access it. The Web UI for Emby refuses to load, yet after a complete reboot it works fine. Is this a bug or is there a setting/procedure somewhere that I'm missing? This could be because you have two containers competing for the same port. Please check your syslogs. Our docker template sets our container to use networking host by default, which allows users to have access to upnp out of the box. If you have another container that is taking over those ports emby might fail to start. Please stop any other containers that might use upnp and report back. Just so you know I have developed and always run emby from my unRAID instance and I have personally never encountered an issue where I need to restart my unRAID server. It has been up for over 300 days. Edited February 17, 2016 by hurricanehrndz 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