Plex server streams at low quality on internal LAN but 1080p over the Internet. What could be causing this?
are you bridging the ip or nat ?
Jun 28, 2019 17:39:27.494 [18412] Debug — Auth: authenticated user 1 as Bizbot
Jun 28, 2019 17:39:27.495 [11256] Debug — Request: [127.0.0.1:55978 (Loopback)] GET /player/proxy/poll?deviceClass=pc&protocolVersion=3&protocolCapabilities=timeline%2Cplayback%2Cnavigation%2Cmirror%2Cplayqueues&timeout=1 (10 live) GZIP Signed-in Token (Bizbot)
Jun 28, 2019 17:39:29.811 [17328] Debug — Auth: authenticated user 1 as Bizbot
Jun 28, 2019 17:39:29.811 [15348] Debug — Request: [127.0.0.1:55176 (WAN)] GET /:/timeline?ratingKey=5323&key=%2Flibrary%2Fmetadata%2F5323&playbackTime=436094&playQueueItemID=23&state=playing&hasMDE=1&time=1004000&duration=4317000 (10 live) TLS GZIP Signed-in Token (Bizbot)
Jun 28, 2019 17:39:29.812 [15348] Debug — Client [nhl5qa3xafxer31688kfyl25] reporting timeline state playing, progress of 1004000/4317000ms for guid=, ratingKey=5323 url=, key=/library/metadata/5323, containerKey=, metadataId=5323, source=
Jun 28, 2019 17:39:29.814 [15348] Debug — Play progress on 5323 ‘The Head Hunter’ - got played 1004000 ms by account 1!
Jun 28, 2019 17:39:29.814 [15348] Debug — [Now] User is Bizbot (ID: 1)
Jun 28, 2019 17:39:29.814 [15348] Debug — [Now] Device is Xbox One (BIZBOT).
Jun 28, 2019 17:39:29.814 [15348] Debug — [Now] Profile is Xbox One
Jun 28, 2019 17:39:29.814 [15348] Debug — [Now] Updated play state for /library/metadata/5323.
Jun 28, 2019 17:39:29.815 [15348] Debug — Statistics: (ez5d4osa6kfj44rlsjxx0guc) Reporting active playback in state 0 of type 1 (scrobble: 0) for account 1
Jun 28, 2019 17:39:29.816 [18412] Debug — Completed: [127.0.0.1:55176] 200 GET /:/timeline?ratingKey=5323&key=%2Flibrary%2Fmetadata%2F5323&playbackTime=436094&playQueueItemID=23&state=playing&hasMDE=1&time=1004000&duration=4317000 (10 live) TLS GZIP 5ms 743 bytes (pipelined: 236)
Jun 28, 2019 17:39:32.892 [13424] Debug — Request: [127.0.0.1:55176 (WAN)] GET /video/:/transcode/universal/dash/5lec6b4l0wygw4v20pe1ep8k/1/156.m4s (10 live) TLS GZIP Signed-in
Jun 28, 2019 17:39:32.893 [13424] Debug — Asked for segment 156 from session.
Jun 28, 2019 17:39:32.893 [13424] Debug — Returning segment 156 from session
Jun 28, 2019 17:39:32.893 [13424] Debug — Content-Length of C:\Users\DBB\AppData\Local\Plex Media Server\Cache\Transcode\Sessions\plex-transcode-5lec6b4l0wygw4v20pe1ep8k-9bc9ab7d-92aa-412b-b59b-69df83482811\init-stream1.m4s,C:\Users\DBB\AppData\Local\Plex Media Server\Cache\Transcode\Sessions\plex-transcode-5lec6b4l0wygw4v20pe1ep8k-9bc9ab7d-92aa-412b-b59b-69df83482811\chunk-stream1-00157.m4s is 136293.
Jun 28, 2019 17:39:32.895 [18412] Debug — Completed: [127.0.0.1:55176] 200 GET /video/:/transcode/universal/dash/5lec6b4l0wygw4v20pe1ep8k/1/156.m4s (10 live) TLS GZIP 3ms 136293 bytes (pipelined: 237) (range: bytes=0-)
Jun 28, 2019 17:39:32.979 [20228] Debug — Session 5lec6b4l0wygw4v20pe1ep8k (4) is unthrottling
Jun 28, 2019 17:39:32.979 [15348] Debug — [Transcoder] Throttle - Getting back to work.
Jun 28, 2019 17:39:33.019 [20228] Debug — Request: [127.0.0.1:56176 (WAN)] GET /video/:/transcode/universal/dash/5lec6b4l0wygw4v20pe1ep8k/0/156.m4s (10 live) TLS GZIP Signed-in
Jun 28, 2019 17:39:33.020 [20228] Debug — Asked for segment 156 from session.
Jun 28, 2019 17:39:33.020 [20228] Debug — Returning segment 156 from session
Jun 28, 2019 17:39:33.020 [20228] Debug — Content-Length of C:\Users\DBB\AppData\Local\Plex Media Server\Cache\Transcode\Sessions\plex-transcode-5lec6b4l0wygw4v20pe1ep8k-9bc9ab7d-92aa-412b-b59b-69df83482811\init-stream0.m4s,C:\Users\DBB\AppData\Local\Plex Media Server\Cache\Transcode\Sessions\plex-transcode-5lec6b4l0wygw4v20pe1ep8k-9bc9ab7d-92aa-412b-b59b-69df83482811\chunk-stream0-00157.m4s is 90333.
Jun 28, 2019 17:39:33.021 [17328] Debug — Completed: [127.0.0.1:56176] 200 GET /video/:/transcode/universal/dash/5lec6b4l0wygw4v20pe1ep8k/0/156.m4s (10 live) TLS GZIP 2ms 90333 bytes (pipelined: 89) (range: bytes=0-)
Jun 28, 2019 17:39:33.157 [13240] Debug — Transcoder segment range: 70 - 164 (164)
Jun 28, 2019 17:39:33.379 [11256] Debug — Session 5lec6b4l0wygw4v20pe1ep8k (4) is throttling
Jun 28, 2019 17:39:33.380 [13424] Debug — [Transcoder] Throttle - Going into sloth mode.
I am streaming from on an Xbox One X from a PC on the same internal subnet. There shouldn’t be any NATing going on. Could you explain what you mean by bridging?
wait you using xbox plex app or you have plex server ?
what does your server status say ?
Plex > status
what quality is your xbox app set for > xbox plex app > settings > quality ?
I have a Windows 10 Pro PC running Plex server which houses the media library. I am streaming from an Xbox with the Xbox Plex app. Both of these devices are in the same local area network.
Under Plex -> Status I see the movie I am currently streaming. However, when I expand it for details it shows my Xbox with a orange exclamation point telling me I have an “indirect” connection. It is baffling since both devices are on the same subnet inside and internal LAN. It also shows the video is being transcoded down from 1080p H.265 to SD H.264.
Quality settings within the Xbox Plex app are set to original, which is the default.
that means you have network problem somewhere, your xbox plex thinks that is not on the same network as your server, so the quality is being reduced.
if you set the xbox plex app remote quality to original, that might help, but the solution to figure out why the client/server think they are not on the same network.
what IP does your xbox stream show on the server, that should be a big pointer… if it is your WAN ip, then you might need to enable
Plex > settings > network > Treat WAN IP As LAN Bandwidth (ENABLE)
you might also want to populate the local network field, just to explicitly tell PMS what is the local network (incase there are multiple networks on your server).
it should look something like 192.168.1.0/24
you can monitor the logs @ Plex > settings > console
to see if you can see any messages that might provide some clues
Do you have DNS rebind protection on your router or DNS server?
I run pfSense for my router/firewall which has DNS rebind protection enabled by default.
DNS Rebinding
Some routers or modems have a feature known as “DNS rebinding protection”, some implementations of which can prevent an app from being able to connect to a Plex Media Server securely on the local network. For most users, this won’t be an issue, but some users of higher-end routers (or those provided by some ISPs) may run into problems.
Similarly, some DNS providers (including some ISPs) may have this feature.
DNS rebinding protection is meant as a security feature, to protect insecurely-designed devices on the local network against attacks. It provides no benefit for devices that are designed and configured correctly.
pfSense DNS Resolver
Similarly, if you are using pfSense’s internal DNS resolver service, you’ll want to adjust that configuration. In the pfSense web UI, go to Services > DNS Resolver, click Display Custom Options, and enter the following the the text box:
server:
private-domain: "plex.direct"
https://support.plex.tv/articles/206225077-how-to-use-secure-server-connections/
1 Like
Network issue or plex setting, windows plex is wired ? is it using cat5 or cat5e ?
Not an ethernet issue. Its the DNS Rebind Protection of Unbound on pfSense. An exception has to be made.
BOOM! I added that custom attribute under the DNS Resolver of pfSense, reset the firewall state tables and immediately the stream is at perfect quality, secure and direct play now.
Achilles, you Sir, are the Plex Ninja of all ninjas!
1 Like
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
