Looks like I can stream smaller video files remotely now without issue, however anything larger like a medium bitrate 1080p movie just sits at buffering and never will actually play. Potentially an unraid issue, as this was not a problem before and the hardware on the server is capable of transcoding way more than a medium 1080p movie.
Hey @ChuckPa so the WAN on the router, on multiple ip checker websites, and on my Plex server all match each other but the problem persists
That’s a transcoding or network bandwidth (what you allow to stream vs your upload limit) issue
Settings - Server - Network - Show Advanced
Settings - Server - Transcoding - Show Advanced (HW acceleration enabled??)
Please confirm for me?
- Your WAN IP starts with 124
- Your WAN IP has ‘138’ in the address
- Your WAN port is 26807
I ask because I’m using the information reported to Plex.tv
There is NO reply from that address/port – Total ‘drop’.
@ChuckPa yes triple checked confirmed all the details you mentioned are correct and are being reflected in the router
Hardware transcoding is enabled, bandwidth isn’t being stressed, CPU & bandwidth usage are at null when trying to play remotely. I’ve tried a handful of movies, about 30% seem to work, the others just sit at buffering and nothing happens.
Running a parity check. Trying to stream the same videos locally is also not loading . . . verified permissions are set correctly. Parity will take 3ish days, I will check back after that with an update.
I have also lost all remote access yesterday on my server. My ISP doesn’t allow port forwarding but I have had no problems in the past year direct playing locally and indirect streaming out of network. Now I can’t even see my server in local network. I even tried to use a VPN port forwarding service to see if that would fix it and it just won’t connect at all. Logs attached.
Plex Media Server Logs_2023-07-31_15-07-58.zip (1.4 MB)
Looks like I’m having the same issue. Can you check mine too please
If you have array parity errors, you’d know it.
Verify DEBUG logging is enabled and VERBOSE is disabled (SAVE if changes)
Start to play
Wait for failure / knowledge it won’t succeed
Download Logs ZIP file from server
Attach ZIP
I’ll be able to see what’s happening.
I tried to ping your server – “No route to host”.
[chuck@lizum ~.2004]$ curl http://XXX.XXX.XXX.3:32400
curl: (7) Failed to connect to XXX.XXX.XXX.3 port 32400: No route to host
[chuck@lizum ~.2005]$
I tried a different way – Infinite loop
Please observe from the Ashburn, VA backbone point
12 * ash-b2-link.ip.twelve99.net (62.115.51.193) 30.410 ms 26.103 ms
13 ash-bb2-link.ip.twelve99.net (62.115.123.124) 29.650 ms 29.560 ms 29.831 ms
14 nyk-bb1-link.ip.twelve99.net (62.115.141.245) 30.250 ms 30.282 ms nyk-bb2-link.ip.twelve99.net (62.115.136.200) 29.246 ms
15 chi-b23-link.ip.twelve99.net (80.91.246.162) 40.000 ms * 39.867 ms
16 62.115.143.165 (62.115.143.165) 45.097 ms 46.434 ms 46.406 ms
17 stlo-b4-link.ip.twelve99.net (62.115.132.218) 62.712 ms 61.244 ms 62.115.143.165 (62.115.143.165) 44.822 ms
18 mediacom-ic-321432.ip.twelve99-cust.net (213.248.85.85) 61.640 ms 63.918 ms 64.990 ms
19 * * *
20 po11.demia001cr1.mchsi.com (68.66.72.62) 74.066 ms 73.921 ms 73.824 ms
21 * * po11.demia001cr1.mchsi.com (68.66.72.62) 76.982 ms
22 * * *
23 * * *
24 63-142-34-170.client.mchsi.com (63.142.34.170) 77.626 ms 76.003 ms *
25 63-142-34-169.client.mchsi.com (63.142.34.169) 79.952 ms 78.613 ms 76.329 ms
26 63-142-34-170.client.mchsi.com (63.142.34.170) 77.665 ms 78.536 ms 63-142-34-169.client.mchsi.com (63.142.34.169) 78.150 ms
27 63-142-34-169.client.mchsi.com (63.142.34.169) 76.767 ms 91.349 ms 81.370 ms
28 63-142-34-170.client.mchsi.com (63.142.34.170) 79.839 ms 76.940 ms 76.720 ms
29 63-142-34-169.client.mchsi.com (63.142.34.169) 81.976 ms 82.775 ms 81.741 ms
30 63-142-34-169.client.mchsi.com (63.142.34.169) 79.897 ms 80.621 ms 63-142-34-170.client.mchsi.com (63.142.34.170) 79.111 ms
31 63-142-34-169.client.mchsi.com (63.142.34.169) 85.644 ms 63-142-34-170.client.mchsi.com (63.142.34.170) 81.397 ms 63-142-34-169.client.mchsi.com (63.142.34.169) 83.565 ms
32 63-142-34-170.client.mchsi.com (63.142.34.170) 81.458 ms 81.184 ms 76.862 ms
33 63-142-34-169.client.mchsi.com (63.142.34.169) 79.983 ms 79.527 ms 77.460 ms
I see “WhiteSky” in the loop here.
Hope that means something to you.
Whitesky is my ISP. Do you think they have done something to block traffic recently? Is this something I need to contact them about? What would I need to ask them to do, if so? TIA
I don’t know if they did it or comcast did it; accidental or otherwise.
I only know that inbound to you, on that port, goes in an infinite loop.
For laughs,
- Turn off Remote Access
- Change the port to 31415 (pi) or sqrt(2) = 14140
- Turn it back on
- Let me know.
- I’ll see what happens
Your server (this instance) is not published at all with Plex.tv
CREATED OVER 2 YEARS AGO
LAST SEEN ABOUT 1 HOUR AGO
PUBLISHED NO
LOCAL ADDRESSES 192.168.68.113
PLATFORM WINDOWS
You need to start checking ports / firewalls / nat port forwarding … the whole sequence from modem/router → computer
Is your LAN address really LOCAL ADDRESSES 100.110.67.241
You DO realize that’s a Public WAN address and not RFC-1918 compliant ?
10.x.x.x.
192.168.x.x
172.16.x.x → 172.31.x.x
You’ve created your own double NAT before leaving the house.
AND –
It’s CGNAT. (Carrier Grade NAT)
Your ISP switched your IP to CGNAT.
You need ask them for a REAL IP
PS: Sorry I’m a bit slow spotting the obvious today
I’m in an apartment complex that only has this option for internet. It’s worked for a year and its just now completely broken and I’m still locked here for a year…
I did ask them for a static IP last year when I moved in since I had to run everything through the Relay and they would not provide me one.
So you’ve been battling this for a year?
Well its never completely shut down before. I could always access locally with no issues and use indirect streaming for remote access which wasn’t that big of a deal since I knew this was always temporary living arrangements.
It’s shut down now because CGNAT routing has been pulled from the BGP tables on the backbone.
It explains why I get “No route to host”.
Your options are limited.
How many people do you allow to stream from you?
If a few. you go one way. If a lot, you go another way
Here’s where it gets ugly – VPN … to get out of your local to the real world.
It’s going to take some captive routing table rules to send ALL TRAFFIC out the VPN and receive from the VPN.
To do this, you need a VPN provider with a real public IP
-and-
that VPN must be up and running before PMS starts (or restarts) so plex.tv gets the correct IP address.
