Jump to content
Luke

Emby Server for Western Digital NAS

Recommended Posts

nyplayer

Great thanks putting it right up.

Share this post


Link to post
Share on other sites
nyplayer

I tried install both the dl2100 and pr4100 and both failed unable to install app. I used manuall install app on both my nases is there something special that needs to be done?

Edited by nyplayer

Share this post


Link to post
Share on other sites
Luke

What error message did it give?

Share this post


Link to post
Share on other sites
alucryd

What's your model? There's one package for each specific WD models, they won't install on other models.

Share this post


Link to post
Share on other sites
nyplayer

5b1450546ec70_Capture.pngWhat's your model? There's one package for each specific WD models, they won't install on other models.

 

I have both dl2100 and pr4100 niether worked.

Edited by nyplayer

Share this post


Link to post
Share on other sites
alucryd

Could you ssh into either of them and go to /mnt/HD/HD_a2/Nas_Prog ? Is there an emby-server folder? Or is it still inside the _install directory?

Share this post


Link to post
Share on other sites
Ranger One

I have the 4TB Model: WDBCTL0040HWT. Are any of those files for my model?

 

Thank's

Dave

Share this post


Link to post
Share on other sites
nyplayer

Could you ssh into either of them and go to /mnt/HD/HD_a2/Nas_Prog ? Is there an emby-server folder? Or is it still inside the _install directory?

 

it is in the _install directory

 

root@MyCloudPR4100 _install # ls

emby-server    module.tar.gz

root@MyCloudPR4100 _install #

 

Edited by nyplayer

Share this post


Link to post
Share on other sites
tafelpoowt

Thanks for the package.

 

The scripts get these arguments:
 

install.sh /mnt/HD/HD_a2/Nas_Prog/_install /mnt/HD/HD_a2/Nas_Prog    # temporary install dir to Nas_Prog (note it doesn't have emby-server in path)
init.sh /mnt/HD/HD_a2/Nas_Prog/emby-server                           # initialize emby-server: add icon to webdir so it can be 'Enabled' nicely in the webUI
start.sh /mnt/HD/HD_a2/Nas_Prog/emby-server                          # start the server - 'Enable' in the webUI
stop.sh /mnt/HD/HD_a2/Nas_Prog/emby-server                           # stop the server - 'Disable' in the webUI
clean.sh                                                             # clean up symlinks and any other requisites of the package
remove.sh                                                            # remove any leftover pids etc, the emby-server directory gets removed anyway

All code looks good, but I believe the install.sh should copy (cp -r) the data instead of moving.

install.sh

UPLOAD_DIR=$1
NAS_PROG=$2

cp -rf $UPLOAD_DIR $NAS_PROG
Edited by tafelpoowt

Share this post


Link to post
Share on other sites
alucryd

Thanks, I'll try that tonight. mv worked fine on my ex2 ultra though.

Share this post


Link to post
Share on other sites
tafelpoowt

The configure button in the web UI doesn't work... so it doesn't redirect you to the application page, even when it's running though (http://ipaddress/emby-server works).

This is caused by the use of CenterType in apkg.rc.

 

And the use of AddonUsedPort: 8096 causes the "configure" button to redirect to http://ipaddress:8096/emby-server/index.html which causes

 

 

Unable to find the specified file.

 

So I suggest to leave CenterType and AddonUsedPort empty.

 

Edit: minor suggestion - plex saves the appdata in /mnt/HD/HD_a2/Nas_Prog/plex_config and then symlinks that dir to /mnt/HD/HD_a2/plex_config ... not sure if that really makes sense, but whatever.

Edited by tafelpoowt

Share this post


Link to post
Share on other sites
nyplayer

Are we going to get a new package that correctly copies emby-server ?

Share this post


Link to post
Share on other sites
nyplayer

Here is my version with the proposed changes (available for a few days only)

 

https://tafelpoowt.stackstorage.com/s/rQC9a3fTTuBQk5f

 

I used the packages in OP, dd to cut off the header (200 bytes) , rename to tar and extract. Made my changes and repackaged.

 

Thank You that worked.

Share this post


Link to post
Share on other sites
nyplayer

Great job works great using PR4100... transcoding working ... livetv working. Everything appears to be working … one thing I would like to do is change the ports to 8097 and 8921 but it appears I cannot to test outside access they revert back to defaults..... I want to temporarily keep EMBY running on my PC for now.

 

Edit

Ignore the part on the ports figured it out.

 

 

Remote transcoding working QuickSync hardware encoding working on PR4100.

Edited by nyplayer

Share this post


Link to post
Share on other sites
Luke

@@tafelpoowt, thanks for helping us figure this out !

 

@@nyplayer, thanks for the testing feedback.

Share this post


Link to post
Share on other sites
Luke

New builds are up in the first post. Thanks everyone.

Share this post


Link to post
Share on other sites
nyplayer

New builds are up in the first post. Thanks everyone.

 

Just a minor thing since I changed the port to 8097 using "configure" in the NAS app it tries to use 8096. 

Edited by nyplayer

Share this post


Link to post
Share on other sites
Luke

 

 

using config in the NAS app

 

What do you mean by this? You have to change it inside of Emby, in order for it to attempt to use a different port. In addition to that, it may require configuration on the NAS side to allow that port.

Share this post


Link to post
Share on other sites
Luke

And the new build installed fine?

Share this post


Link to post
Share on other sites
Luke

Ok I think I know what you mean. The configure button in WD opens the web app to the wrong port. I'm not really sure what we can do there since that action is hard-coded into the package itself.

 

In fact, the best thing I can think of would be to not allow you to configure the port in the first place.

Share this post


Link to post
Share on other sites
tafelpoowt

If you want to change the port of a service on the WD OS3 platform, you have to edit the scripts in /shares/Volume_1/Nas_Prog/emby-server via SSH.

In this case, modify the redirect URL in /shares/Volume_1/Nas_Prog/emby-server/web/index.html

 

The same applies to any WD app.

Edited by tafelpoowt

Share this post


Link to post
Share on other sites
nyplayer

What do you mean by this? You have to change it inside of Emby, in order for it to attempt to use a different port. In addition to that, it may require configuration on the NAS side to allow that port.

 

The configure is what you use to bring up the web page when logged into the NAS .... If I click on Configure it tries to open the dashboard using 8096 even though I changed it to 8097.

 

 

5b15b835c4e31_Capture.png

Share this post


Link to post
Share on other sites
Luke

Ok right, the only way to handle this is with the manual process that @@tafelpoowt outlined above.

 

Based on this, it is my opinion that we should just hide the port configuration for WD and not let you change it in the first place. If you're willing to make the manual change above, then you can also manually edit the server's configuration file.

Share this post


Link to post
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...