Plex for Xbox One has stopped working.

So a few weeks ago there were updates to the Plex server and I think a small one to the xbox one app. Now nothing works. Nadda. Direct play files, nope, stutters. Transcoded files? same thing.

My cpu uses all of 5% to playback items. I have 16 gigs of memory, use max 27%.

Read about it here - http://forums.plex.tv/discussion/272240/massive-stuttering-help#latest

I’ve never ever had a problem so long as the apps were working.

I’m at a complete loss. Any help would be very welcomed. My plex is now almost entirely useless.

According to your logs the only things that stand out are:
May 23, 2017 18:06:24.934 [14120] WARN - [Plex for Xbox One] Player: Excessive buffering detected; network

That is saying the xbox isn’t getting the file fast enough and that is causing buffering. Since the file is direct playing that means the server isn’t sending out data fast enough. Either it can’t read it or can’t get it out fast enough (or possibly getting lost in the network).

May 23, 2017 18:05:26.733 [15364] DEBUG - PublicAddressManager: got WAN IP 10.0.0.8 from router
May 23, 2017 18:05:26.733 [15364] WARN - PublicAddressManager: WAN IP is a private IP address

Did anything change in your network configuration that would cause traffic to route in a weird way or anything that could be causing interference with your wireless bridge? Is there any way to run a temporary cable to see if the WiFi bridge is the issue?

The problem trying to troubleshoot this is that since it is directly played the Xbox One downloads the original file from the server and it is treated just like a file transfer. So it is normally down to a drive read speed or a network connection. Have you tried downloading the file over the same path to see if the speed is maintained up? (IE if you have it playing on the Xbox One and downloading the file from the server from Plex Web)

Most of these questions are based on the fact that you are seeing the same results on a number of different clients that should (mostly) all be direct playing this media which means that they should all be acting like a simple file transfer.

Hmmmm…very interesting observations. Nothing that I’ve noticed has changed at all. My routers diagnostics show a constant 1153 mbit connection from the bridge itself with a 866 mbit connection from my pc. I’ll play around a bit and let you know what I find.

@jmckee said:
According to your logs the only things that stand out are:
May 23, 2017 18:06:24.934 [14120] WARN - [Plex for Xbox One] Player: Excessive buffering detected; network

That is saying the xbox isn’t getting the file fast enough and that is causing buffering. Since the file is direct playing that means the server isn’t sending out data fast enough. Either it can’t read it or can’t get it out fast enough (or possibly getting lost in the network).

May 23, 2017 18:05:26.733 [15364] DEBUG - PublicAddressManager: got WAN IP 10.0.0.8 from router
May 23, 2017 18:05:26.733 [15364] WARN - PublicAddressManager: WAN IP is a private IP address

Did anything change in your network configuration that would cause traffic to route in a weird way or anything that could be causing interference with your wireless bridge? Is there any way to run a temporary cable to see if the WiFi bridge is the issue?

The problem trying to troubleshoot this is that since it is directly played the Xbox One downloads the original file from the server and it is treated just like a file transfer. So it is normally down to a drive read speed or a network connection. Have you tried downloading the file over the same path to see if the speed is maintained up? (IE if you have it playing on the Xbox One and downloading the file from the server from Plex Web)

Most of these questions are based on the fact that you are seeing the same results on a number of different clients that should (mostly) all be direct playing this media which means that they should all be acting like a simple file transfer.

OK, so I ran a whole slew of tests and scenarios. First started by uninstalling and re-installing my ethernet drivers on the server, upgraded the firmware on the bridge, redid bridge and server connections and finally when that didn’t do anything I ran a long ethernet cord directly from the pc to the router. Nothing different.

I tried direct stream, direct play combinations, etc…

My guess is whatever is happening it MUST be server software related and has to do with dishing out the video streams. It’s like someone took a buffer cache and made it too small. Some videos on Android TV are getting weird messages that the server isn’t available, when clearly it is. I’m guessing someone simply screwed up and borked it. I’m sure there will be a fix, just a matter of when. There’s been 2 major times in the past when I’ve had to wait up to a month for plex to get it’s act together. I guess this is time 3. :frowning:

I have been experiencing the same, and from reading around many others are as well. Since 1.6 at least, both the xbox one and chromecast have been broken. chromecast wont play AC3 audio anymore, and xbox one is completely useless for plex. Direct Play for files stutters like crazy through plex, but the same file played from USB or from network will play fine.

I can add that I have been having issues since a couple patches ago to the server side software. I can start a video and about 30 sec to 1 min into the video it stops and according to the server, the stream is buffering. This lasts for a few minutes before it plays again for about 10 seconds then starts buffering all over again.

I did a reinstall of the server software and it was all working for a couple hour long episodes, then started again with the same issue.

I haven’t made any changes to the network, although after this started happening I did do a reset and reconfigure on the router which had no effect. The network is all wired with no wifi. I tested with my old router which everything worked on and the same issue occurs.

If I use the media player on the Xbox one, it can see the Plex media and play the videos fine.

Any takers for 1.7.3 yet? I slept on upgrading to 1.6x because of a few reports along these lines with the XB1 client.