Theodore 136 Posted November 24, 2019 Posted November 24, 2019 I just upgraded to 4.3.0.26 and have encountered these 2 issues so far: 1) I cannot disable remote control/mirroring. I use the web portal to access Emby and start a stream to my MPC. When I select the MPC as the output and navigate in the web portal the MPC follows along - even to content the MPC user does NOT have access to. Like in all previous versions the MPC should not be following the bread trail with the connected controller. 2) Running as a service is broken. I have started Emby as a service with NSSM since 2.0.x.x and this update has broken that function. As Emby is running on a Server OS, running as a service HAS to be an option.
Luke 42077 Posted November 24, 2019 Posted November 24, 2019 2) Running as a service is broken. I have started Emby as a service with NSSM since 2.0.x.x and this update has broken that function. As Emby is running on a Server OS, running as a service HAS to be an option. Why do you feel this way? Others are able to run it as a service.
Happy2Play 9780 Posted November 24, 2019 Posted November 24, 2019 I just did a nssm service install for stable release and had no issues.
Theodore 136 Posted November 24, 2019 Author Posted November 24, 2019 (edited) Why do you feel this way? Others are able to run it as a service. I was able to fix it by completely removing the existing service with NSSM then re-creating it but leaving the "-service" argument off of it this time. That argument appears to have been removed from this version of the executable and that was what was breaking it. I will be honest though, it makes no sense to me why y'all haven't made running as a service for the server application a default. Regardless of whether people run it on a workstation or on a server OS, they don't interact with Emby Server through a native application at all. Interactions are either through a web portal or through a secondary app (i.e. Theater). Why not just make it a Windows service by default? Edited November 24, 2019 by Theodore
Luke 42077 Posted November 24, 2019 Posted November 24, 2019 I was able to fix it by completely removing the existing service with NSSM then re-creating it but leaving the "-service" argument off of it this time. Well, I wouldn't do that because that will cause features to be enabled when running as a service that shouldn't be enabled. But it's possible you may never notice a problem and be able to get away with it.
Theodore 136 Posted November 24, 2019 Author Posted November 24, 2019 Well, I wouldn't do that because that will cause features to be enabled when running as a service that shouldn't be enabled. But it's possible you may never notice a problem and be able to get away with it. I didn't exactly have a choice, it wouldn't start with the -service argument. Are you saying it is still there and I should try again? Also, what about my other issue and question?
Luke 42077 Posted November 24, 2019 Posted November 24, 2019 I didn't exactly have a choice, it wouldn't start with the -service argument. Are you saying it is still there and I should try again? Also, what about my other issue and question? Yes, we should look at whatever the issue is. But after applying an update, you should always start once with the tray icon app just in case there might be any mandatory user interaction required. Then shut down and you can run your service.
Luke 42077 Posted November 24, 2019 Posted November 24, 2019 I will be honest though, it makes no sense to me why y'all haven't made running as a service for the server application a default. Regardless of whether people run it on a workstation or on a server OS, they don't interact with Emby Server through a native application at all. Interactions are either through a web portal or through a secondary app (i.e. Theater). Why not just make it a Windows service by default? You're not the one who has to troubleshoot and support users all day long. Back when we used to have the service, it was extremely painful because many users do not understand the concept of the service account and what permissions it has. That leads to users getting frustrated and yelling at us that "emby doesn't work", when in fact they didn't grant the service account access to something that it needs. Running as a service by default will only result in loss of users. People will bail because it will be too hard for them to setup.
Theodore 136 Posted November 24, 2019 Author Posted November 24, 2019 Yes, we should look at whatever the issue is. But after applying an update, you should always start once with the tray icon app just in case there might be any mandatory user interaction required. Then shut down and you can run your service. That seems to have done it. I stopped the service and edited back the -service argument then manually ran the Emby application. It took a while to kick off and go, but after letting the library refresh the service was able to start successfully after a reboot. Now that part 2 is resolved, part 1? How do I disable the screen mirror/breadcrumb follow?
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