Jump to content

Emby Server for Western Digital NAS


Recommended Posts

Françoise

Change the url in your browser to just:

http://{address}:8096

We'll resolve that redirect for the next update. thanks.

 

I did try to change the url. it made no difference. It went back to /web/wizardstart.html, which wasn't displayed correctly.
 
As I mentioned, it was fine on the tafelpoowt build. 
 

 

 

It might be worth mentioning that I can't uninstall Emby server using the MyCloud interface.

 

After rebooting the device, I was able to uninstall Emby.
Link to post
Share on other sites
nyplayer

The wizard should be fine with the next version. Thanks.

 

working with new release.... but when I click on settings on the right it does not bring me to dashboard... instead i have to browse down and click on server dashboard … too many clicks. Can't it just go to the dashboard the way it used to be ?

 

noe to go direct to dashboard I have to use this http://10.0.0.144:8096/web/index.html#!/dashboard.html

Edited by nyplayer
Link to post
Share on other sites

Hello all. First post.

 

I'm a Plex user and am trying to install Emby to consider a move over.

 

I have a PR2100 and am struggling with the Emby installation.

emby-server-western_digital_pr2100_3.4.1.18_x86_64

 

 

I've read the previous comments and understand that others have worked around using the alternate package and then updating.

 

I can't do that. Regardless of using the manual install, or the NAS UI install, the results are the same.

 

I end up with either the

 

${WelcomeToProject}${ButtonQuickStartGuide}

${ThisWizardWillGuideYou}

 

 

 

 

 

page for http://192.168.0.6:8096/web/wizardstart.html

 

or, if I rely on the webserver redirecting me, http://192.168.0.6:8096 takes me to an infinite redirect.

 

What have I done, or got different? The logs are littered with a DLNA socket error, and I cant see why, or if it is relevant (bear in mind Plex is coexisting on this hardware):

 

018-06-23 01:05:49.199 Error Dlna: Error in BeginListeningForBroadcasts
    *** Error Report ***
    Version: 3.4.1.18
    Command line: /mnt/HD/HD_a2/Nas_Prog/emby-server/system/EmbyServer.dll -programdata /mnt/HD/HD_a2/emby -ffmpeg /mnt/HD/HD_a2/Nas_Prog/emby-server/bin/ffmpeg -ffprobe /mnt/HD/HD_a2/Nas_Prog/emby-server/bin/ffprobe -updatepackage emby-server-emby-server-western_digital_pr2100_{version}_x86_64.bin -nolocalportconfig
    Operating system: Unix 4.1.13.0
    64-Bit OS: True
    64-Bit Process: True
    User Interactive: True
    Processor count: 4
    Program data path: /mnt/HD/HD_a2/emby
    Application directory: /mnt/HD/HD_a2/Nas_Prog/emby-server/system
    System.Net.Sockets.SocketException (98): Address already in use
       at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName)
       at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
       at System.Net.Sockets.Socket.Bind(EndPoint localEP)
       at Emby.Server.Implementations.Net.UdpSocket..ctor(Socket socket, Int32 localPort, IPAddress ip)
       at Emby.Server.Implementations.Net.SocketFactory.CreateUdpMulticastSocket(String ipAddress, Int32 multicastTimeToLive, Int32 localPort)
       at Rssdp.Infrastructure.SsdpCommunicationsServer.ListenForBroadcastsAsync()
       at Rssdp.Infrastructure.SsdpCommunicationsServer.BeginListeningForBroadcasts()
    System.Net.Sockets.SocketException
       at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName)
       at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
       at System.Net.Sockets.Socket.Bind(EndPoint localEP)
       at Emby.Server.Implementations.Net.UdpSocket..ctor(Socket socket, Int32 localPort, IPAddress ip)
       at Emby.Server.Implementations.Net.SocketFactory.CreateUdpMulticastSocket(String ipAddress, Int32 multicastTimeToLive, Int32 localPort)
       at Rssdp.Infrastructure.SsdpCommunicationsServer.ListenForBroadcastsAsync()
       at Rssdp.Infrastructure.SsdpCommunicationsServer.BeginListeningForBroadcasts()
 

 

I'm using the most up to date NAS firmware, and the most recent Emby install, for the PR2100.

 

Apologies if this should be in a new thread, but I've got problems that have been mentioned in this one, so thought it best to start here.

 

 

Thanks.

Link to post
Share on other sites

hi @@ooger, welcome. that redirect issue with the wizard is just an issue in the current beta server, and since this package is based on that it's also affecting this. i'm hoping to have that resolved by tomorrow. thanks.

Link to post
Share on other sites

That makes sense. I'll check back later in this case then.

 

I noticed a new revision had been published overnight recently so can see you're obviously busy.

 

Thanks for letting me know.

Link to post
Share on other sites

I'm seeing no difference in the redirect behaviour, but can confirm Ive done an upgrade and an uninstall/reinstall on 3.4.1.19.

 

Im being taken  by the configure button to

 

http://192.168.0.6/emby-server/index.html

which then goes to

http://192.168.0.6:8096/web/index.html#!/wizardstart.html- which obviously fails (Firefox has detected that the server is redirecting the request for this address in a way that will never complete.)

 

- http://192.168.0.6:8096/

has the same result

 

Any ideas please?

Link to post
Share on other sites

I don't want to interrupt the workflow, but should I, or is it preferred to, upgrade my beta from (...13) to (...19)? (I know the server doesn't say anything because it's a beta.)

 

Thanks, and sorry for breaking the flow. :ph34r:

Link to post
Share on other sites

Sorry @@Luke. Upgrade won't take on my DL4100. Hole new problem maybe.

 

I'm just glad the DL4100 rejected it and, after a reboot, is still happy with (...13). Haven't checked everything connected yet.

Link to post
Share on other sites
tafelpoowt

Aight... I had a look again and found the issue: https://security.stackexchange.com/questions/160183/openssl-1-0-1t-does-not-decrypt-with-bf-if-encrypted-with-openssl-version-1-1-0

 

The mksapkg tool creates an apkg signature with openssl, which defaults to SHA256 as of openssl version 1.1.x.

The firmware still has openssl v1.0.1m  (19 Mar 2015), so it expects an MD5 sum, not an SHA256 sum.

root@MyCloudPR4100 emby-server # openssl version
OpenSSL 1.0.1m 19 Mar 2015
root@MyCloudPR4100 emby-server # openssl bf-cbc -d -in apkg.sign -k Lidho.mdk3K3h -md sha256
emby-server
root@MyCloudPR4100 emby-server # openssl bf-cbc -d -in apkg.sign -k Lidho.mdk3K3h 
bad decrypt
140435311855248:error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt:evp_enc.c:516:

Short term solution is to build the package in an environment with an older 1.0.x openssl version (I suggest to use docker).

I'll contact WD devs for a solution... either in the firmware but probably in the mksapkg tool.

 

EDIT: I had Ubuntu 16.04 (openssl 1.0.2g) when creating my first package. I've upgraded in recently to 18.04 (1.1.0g) and also failed to create a proper package since...

Edited by tafelpoowt
Link to post
Share on other sites

Just downloaded v20 for the pr2100 and I have the same symptoms that were there when I first posted, all roads lead to an infinite http redirect.

 

Is there a stable version?

 

 

Link to post
Share on other sites

Yes definitely installed. I can access Emby through my iPhone using the app and verify the version. Just no web interface to configure anything.

Link to post
Share on other sites
tafelpoowt

@@tafelpoowt after your edit are you still sure this is the issue?

 

Sorry for the delay... yeah I'm sure that is the issue. I added an edit to clarify why I've been seeing the same installation issue since upgrading my local system.

I also checked all signatures of all my apps and they are all MD5 hashed, only emby server was SHA256.

 

What is the openssl version on the build system you are using?

 

I added a dockerfile on https://github.com/WDCommunity/wdpksrc with an Ubuntu 16.04 environment.

Link to post
Share on other sites
tafelpoowt

Here's a suggestion for the installation instructions on the https://emby.media/download.html page:

  1. Download emby-server-xxx.bin
  2. In the web interface of your My Cloud device, go to the Apps tab
  3. Select 'Manual Install' and install Emby Server
  4. Select Emby Server in the list of installed apps
  5. Click configure to setup Emby Server. It redirects to http://<ipaddr>:8096

At the moment, the installation instructions refer to localhost, which will probably not work ;-)

Edited by tafelpoowt
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...