Jump to content

Emby not visible on Xbox One with server 3.0.5873.0


tobias-tobin

Recommended Posts

tobias-tobin

I am not posting this as a problem necessarily.  I am just wondering if Emby has disappeared from Media Player on Xbox One for anyone else?  We have multiple units and it does not show up on any of them.  Although, on the server, I see the Xbox's connected.  I am wondering if maybe I have done something or Xbox has?

 

BTW - I have another DLNA server (Subsonic) and it is showing up as usual and working.

Edited by tobias-tobin
Link to comment
Share on other sites

tobias-tobin

I see in the server release today a dlna uuid fix so i assume that will fix it.  Cannot put as it is being used ATM but thank you.

Link to comment
Share on other sites

Was about to post a similar issue, but haven't fully investigated yet.

 

I installed 3.0.5870.0 from the stable branch and following the database upgrade, my dlna clients are experiencing issues with not being able to even see the Emby server.

PS3

XboxOne

Sony BDP-S390

Sony BDP-S5100

 

I know the 5100 cannot see the server at all, I am investigating the others.

Link to comment
Share on other sites

Happy2Play

Was about to post a similar issue, but haven't fully investigated yet.

 

I installed 3.0.5870.0 from the stable branch and following the database upgrade, my dlna clients are experiencing issues with not being able to even see the Emby server.

PS3

XboxOne

Sony BDP-S390

Sony BDP-S5100

 

I know the 5100 cannot see the server at all, I am investigating the others.

3.0.5880-beta

 

•Update linux ffmpeg

•Update filter dialogs

Dlna server fixes

Link to comment
Share on other sites

Good news. Hopefully it comes out of beta quickly. Currently my main DLNA client is completely inop with Emby on the stable branch. 

 

Do you know if it would be helpful at all to provide debug logs? I did capture them just in case.

Link to comment
Share on other sites

Hmmm, updated with the beta branch, Version 3.0.5880.0 still no joy seeing the server from various DLNA clients:

 

XBOXOne

BDP-S5100

BDP-S390

 

Haven't tested PS3 yet... Any ideas?

 

Edited to attach full debug server log from stable branch. It looks from the log as though everything should be working, but I have the same behavior now on the beta branch as I did on the stable branch. My DLNA clients, listed above, cannot see the Emby server at all.

server-nodlnabdpbrowse.7z

Edited by GB Utah
Link to comment
Share on other sites

All I can tell is I reproduced the issue easily over the last several days since it was reported. After the fix I made today, I have no problems seeing the server now from an xbox one and other devices.

 

the dlna server has not really seen many changes over the last couple months. even the "fix", really only reverted a change that was made a couple weeks ago.

Link to comment
Share on other sites

Observations (Emby restarted after every step/observation):

 

Waited for stable branch yesterday to fully update, including database upgrade.

Within minutes turned on Blu-ray player, noted Emby not available.

Removed all connection servers from Blu-ray, still no Emby.

Factory reset Blu-ray, still no Emby.

Remove user DLNA profiles from Emby, still no Emby on Blu-ray player.

Change DLNA Client Discovery and Alive message intervals to 15 and 10 respectively, still no Emby on Blu-ray player.

Reinstall Emby from website, still no Emby viewable on Blu-ray player.

Turn on server debug logging and DLNA debug logging, capture logs as seen above.

 

Install Emby beta branch, still no Emby on Blu-ray nor Xbox One.

 

Has to be something....... This was working literally seconds before my Emby was upgraded on the stable branch

Link to comment
Share on other sites

Attaching full debug log from beta branch.

 

I enabled server debug logging and DLNA debug logging. Restarted server, restarted blu-ray, updated the connection server list within the blu-ray. Still no evidence of Emby from within the blu-ray player.

 

Would these steps/logs be useful from attempting with the XBOX One as well?

server-63591249463.7z

Link to comment
Share on other sites

Happy2Play

Just a guess but could there be a conflict with your AsusWRT dlna and Emby?

Link to comment
Share on other sites

Here's my debug log with my XBOX One attempt and the beta branch installed.

 

In response to Happy, it's possible in the past or in other's cases there was a conflict with the DLNA server on AsusWRT, but I do not run that DLNA server at the moment and haven't for quite some time. It is disabled on the router.

 

Again, these clients were working 100% before the stable branch update yesterday. We were using two of them at the time I restarted the server to update the database for the stable branch update. Ever since Emby came back online following that update, DLNA is completely inoperable here on my clients:

XBOX One

BDP-S5100

BDP-S390

 

Emby applications do not appear to be affected in my home, but we rely about 90% on DLNA.....

server-63591250215.7z

Link to comment
Share on other sites

I'm beginning to wonder if I should start a new thread?

 

 

I took a slightly longer look at my logs and some of the commits on GitHub. I noticed the following commit comment:

 

5 Feb 2016

ensure server reports consistent uuid

 

From my logs I present the following:

2016-02-15 13:03:35.0054 Debug SsdpHandler: Sending alive notifications
2016-02-15 13:03:35.0054 Debug SsdpHandler: uuid:696d0327d9e9e5b7966909ef473ce628::upnp:rootdevice said alive
2016-02-15 13:03:35.0054 Debug SsdpHandler: uuid:696d0327d9e9e5b7966909ef473ce628::urn:schemas-upnp-org:device:MediaServer:1 said alive
2016-02-15 13:03:35.0054 Debug SsdpHandler: uuid:696d0327d9e9e5b7966909ef473ce628::urn:schemas-upnp-org:service:ContentDirectory:1 said alive
2016-02-15 13:03:35.0054 Debug SsdpHandler: uuid:696d0327d9e9e5b7966909ef473ce628::urn:schemas-upnp-org:service:ConnectionManager:1 said alive
2016-02-15 13:03:35.0054 Debug SsdpHandler: uuid:696d0327d9e9e5b7966909ef473ce628::urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1 said alive
2016-02-15 13:03:35.0054 Debug SsdpHandler: uuid:696d0327d9e9e5b7966909ef473ce628 said alive
2016-02-15 13:03:35.0054 Debug SsdpHandler: Registered mount 696d0327-d9e9-e5b7-9669-09ef473ce628 at http://192.168.1.207:8096/dlna/696d0327d9e9e5b7966909ef473ce628/description.xml
2016-02-15 13:03:35.0054 Debug SsdpHandler: Sending alive notifications
2016-02-15 13:03:35.0054 Debug SsdpHandler: uuid:696d0327d9e9e5b7966909ef473ce628::upnp:rootdevice said alive
2016-02-15 13:03:35.0054 Debug SsdpHandler: uuid:696d0327d9e9e5b7966909ef473ce628::urn:schemas-upnp-org:device:MediaServer:1 said alive
2016-02-15 13:03:35.0054 Debug SsdpHandler: uuid:696d0327d9e9e5b7966909ef473ce628::urn:schemas-upnp-org:service:ContentDirectory:1 said alive
2016-02-15 13:03:35.0054 Debug SsdpHandler: uuid:696d0327d9e9e5b7966909ef473ce628::urn:schemas-upnp-org:service:ConnectionManager:1 said alive
2016-02-15 13:03:35.0054 Debug SsdpHandler: uuid:696d0327d9e9e5b7966909ef473ce628::urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1 said alive
2016-02-15 13:03:35.0054 Debug SsdpHandler: uuid:696d0327d9e9e5b7966909ef473ce628 said alive
2016-02-15 13:03:35.0054 Debug SsdpHandler: uuid:7b5090d37596b391ff39de9346a2872e::upnp:rootdevice said alive
2016-02-15 13:03:35.0054 Debug SsdpHandler: uuid:7b5090d37596b391ff39de9346a2872e::urn:schemas-upnp-org:device:MediaServer:1 said alive
2016-02-15 13:03:35.0054 Debug SsdpHandler: uuid:7b5090d37596b391ff39de9346a2872e::urn:schemas-upnp-org:service:ContentDirectory:1 said alive
2016-02-15 13:03:35.0054 Debug SsdpHandler: uuid:7b5090d37596b391ff39de9346a2872e::urn:schemas-upnp-org:service:ConnectionManager:1 said alive
2016-02-15 13:03:35.0054 Debug SsdpHandler: uuid:7b5090d37596b391ff39de9346a2872e::urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1 said alive
2016-02-15 13:03:35.0054 Debug SsdpHandler: uuid:7b5090d37596b391ff39de9346a2872e said alive
2016-02-15 13:03:35.0054 Debug SsdpHandler: Registered mount 7b5090d3-7596-b391-ff39-de9346a2872e at http://192.168.1.156:8096/dlna/7b5090d37596b391ff39de9346a2872e/description.xml
2016-02-15 13:03:35.0210 Debug IDeviceDiscovery: NOTIFY Device message received from 192.168.1.207:1900. Headers: HOST=239.255.255.250:1900,CACHE-CONTROL=max-age = 600,LOCATION=http://192.168.1.207:8096/dlna/696d0327d9e9e5b7966909ef473ce628/description.xml,SERVER=WIN64/6.2 UPnP/1.0 DLNADOC/1.5 Emby/3.0.5870.0,NTS=ssdp:alive,NT=upnp:rootdevice,USN=uuid:696d0327d9e9e5b7966909ef473ce628::upnp:rootdevice
2016-02-15 13:03:35.0210 Debug IDeviceDiscovery: NOTIFY Device message received from 192.168.1.156:1900. Headers: HOST=239.255.255.250:1900,CACHE-CONTROL=max-age = 600,LOCATION=http://192.168.1.156:8096/dlna/7b5090d37596b391ff39de9346a2872e/description.xml,SERVER=WIN64/6.2 UPnP/1.0 DLNADOC/1.5 Emby/3.0.5870.0,NTS=ssdp:alive,NT=upnp:rootdevice,USN=uuid:7b5090d37596b391ff39de9346a2872e::upnp:rootdevice

Stable branch immediately following update to 5870. DLNA clients lost visibility of Emby DLNA server. This was before I removed some other devices from my network, namely a AFTV2

2016-02-16 19:57:58.6837 Debug SsdpHandler: Sending alive notifications
2016-02-16 19:57:58.6837 Debug SsdpHandler: uuid:7b5090d37596b391ff39de9346a2872e::upnp:rootdevice said alive
2016-02-16 19:57:58.6837 Debug SsdpHandler: NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age = 600
LOCATION: http://192.168.1.156:8096/dlna/7b5090d37596b391ff39de9346a2872e/description.xml
SERVER: WIN64/6.2 UPnP/1.0 DLNADOC/1.5 Emby/3.0.5880.0
NTS: ssdp:alive
NT: upnp:rootdevice
USN: uuid:7b5090d37596b391ff39de9346a2872e::upnp:rootdevice

                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           
2016-02-16 19:57:58.6837 Debug SsdpHandler: NOTIFY message received from 192.168.1.156:58939 on 0.0.0.0:1900. Headers: HOST=239.255.255.250:1900,CACHE-CONTROL=max-age = 600,LOCATION=http://192.168.1.156:8096/dlna/7b5090d37596b391ff39de9346a2872e/description.xml,SERVER=WIN64/6.2 UPnP/1.0 DLNADOC/1.5 Emby/3.0.5880.0,NTS=ssdp:alive,NT=upnp:rootdevice,USN=uuid:7b5090d37596b391ff39de9346a2872e::upnp:rootdevice
2016-02-16 19:57:58.6837 Debug IDeviceDiscovery: NOTIFY Device message received from 192.168.1.156:1900. Headers: HOST=239.255.255.250:1900,CACHE-CONTROL=max-age = 600,LOCATION=http://192.168.1.156:8096/dlna/7b5090d37596b391ff39de9346a2872e/description.xml,SERVER=WIN64/6.2 UPnP/1.0 DLNADOC/1.5 Emby/3.0.5880.0,NTS=ssdp:alive,NT=upnp:rootdevice,USN=uuid:7b5090d37596b391ff39de9346a2872e::upnp:rootdevice
2016-02-16 19:57:58.6837 Debug IDeviceDiscovery: NOTIFY Device message received from 192.168.1.156:58939. Headers: HOST=239.255.255.250:1900,CACHE-CONTROL=max-age = 600,LOCATION=http://192.168.1.156:8096/dlna/7b5090d37596b391ff39de9346a2872e/description.xml,SERVER=WIN64/6.2 UPnP/1.0 DLNADOC/1.5 Emby/3.0.5880.0,NTS=ssdp:alive,NT=upnp:rootdevice,USN=uuid:7b5090d37596b391ff39de9346a2872e::upnp:rootdevice

After upgrading to the beta branch. DLNA clients still cannot see Emby server at all.

 

I'm no expert on the Emby code, but from the logs it definitely appears as though the server is not reporting itself accurately/completely to clients when it sends the 'alive notification'

 

Any ideas?

 

 

 

 

 

 

 

 

 

 

 

Edit: Removed claim I had debug log from before stable branch update. Unfortunately, I don't.

Edited by GB Utah
Link to comment
Share on other sites

dansblackcat

Dlna has stopped working on my Sony TV.  I'm having the same issues as others where my device wont see the Emby server.

The Emby server sees my TV and so too does the emby app on my Phone and Tablet.  I can successfully play files from my devices to my TV.

 

It's my spare TV that I don't really use so I have no idea when it stopped working nor have I investigated further yet. 

Link to comment
Share on other sites

Hmmm again....

 

Version 3.0.5891.30026

 

I just updated to the dev branch, and I can now see Emby DLNA server again on my BDP-S5100. Not clear what changed yet, but for what it's worth.

 

 

Edited to add: Working on Xbox One also...

Edited by GB Utah
Link to comment
Share on other sites

LqHnyBear

It doesn't appear to fix it with version 3.0.5882. I can see my browsers, ipad, iphone but I can't see the XBOX One or my Samsung TV. It was all working fine 2 updates ago.

Link to comment
Share on other sites

dansblackcat

3.0.5582 fixed the issue on my Sony TV.  I can now see the emby server again.

Only thing not working correctly is the artwork.  Folders are just a generic image of a folder and not proper image covers.

Only image that seems to work are the thumbnails for the individual episodes.

Link to comment
Share on other sites

LqHnyBear

It was working again on Version 3.0.5883.0 to Version 3.0.5885.0 but now with versions Version 3.0.5886.0 and Version 3.0.5887.0 I can't see my Samsung TV or Xbox One again.

Edited by LqHnyBear
Link to comment
Share on other sites

It was working again on Version 3.0.5883.0 to Version 3.0.5885.0 but now with versions Version 3.0.5886.0 and Version 3.0.5887.0 I can't see my TV or Xbox One again.

 

there are no differences between any of these builds. when you open the media player app, be patient. it may take up to a minute to appear.

Link to comment
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...