Consistently buffering remotely

Server Version#: 4.141.0
Player Version#: N/A

Hi All,

I’ve done a fair amount of digging reviewing other posts, but unfortunately I haven’t found an answer.

When watching Plex locally, I have no issues at all. However when watching remotely, it is extremely slow and constantly buffering.
I have the hardware and bandwidth available to sufficiently allow streaming over the WAN.




Remote Access is green and ticked. I am also using a custom port.

I have confirmed with my ISP that they are not throttling the traffic.

I have a static IP address, so I’m not on CGNAT.

I’m running out of ideas.

In the console on Plex, I saw these 2 errors, but they haven’t provided me much insight into the issue.

“Sending data was too slow, timed out”

“Failed to stream media, client probably disconnected after 491520 bytes: 10054 - An existing connection was forcibly closed by the remote”
Also, Plex Relay is off.

This isn’t OS related, as I also tried this on my Ubuntu server, with the same issue.

Please could I ask if anyone is able to advise?

I have the same issue. Did you ever find a solution?

Is it a direct stream or is plex transcoding? server logs may provide some insight

The Server Version# you listed is actually the Web Player Version#. You want to go to settings > general and there you will find the server version number. I imagine the player/client version number could be helpful in this case as well.

As @dbirch said server logs will be needed.

Is this problem on all media? What type of internet connection does the remote client have? Are you transcoding or direct playing?

Hi All,

I’d like to apologize for the rudeness with not replying to you all who were kindly trying to help.

I’ve done some further testing and I have tested this on Ubuntu and Windows Server (the same host. I reinstalled the OS). I have also tested this on my gaming PC (Windows 11) and I have the same result.

I am thinking the issue lies with my router.

I did have a ASUS RT86U, which I’ve just upgraded today for a RT-AX88U due to the 86U being end of life. Unfortunately I have the same issue.
However if streaming internally works perfectly with no issue, but streaming remotely keeps buffering, I believe it must be at the router level.
On the router, I have disabled all the AI features such as “AiProtection”, “Adaptive QoS” and “Traffic Analyzer”.
I have also disabled DoS protection on the router as a test, yet I still have the same issue with it buffering. Sadly I am out of ideas.
Has anyone else had issues who use a Asus router with remote streaming buffering?
The only other test I can think of now is to plugin my ISPs router and test it on that.

To add on, I am testing with Direct Play, so no Transcoding is being done

Sounds like you are having issues with your upload speed then.

My upload speed is 800-900Mbps, which thankfully is far more than I need for Plex streaming and other things.
Latest speedtest result from my server.

In the logs, I see this happen when it buffers

Feb 28 11:25:37 kernel: DROP IN=eth0 OUT= MAC=c8:7f:54:e5:bd:20:88:90:09:83:30:2f:08:00 SRC=REMOVED DST=REMOVED LEN=60 TOS=0x00 PREC=0x00 TTL=55 ID=37496 PROTO=TCP SPT=49098 DPT=32400 SEQ=2970377396 ACK=0 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (0204053E0402080AA5D374C60000000001030309) MARK=0x8000000

It looks like I’ve resolved the issue ive been having.
So despite changing ISP (for other reasons) and router (other reasons included), the issue remained.
In addition, my internet has worked perfectly for gaming, downloading, streaming from other services. No packet loss or download issues.
However, i changed my ethernet cable from the router to the ONT from a CAT5 cable to a CAT6 cable and now Plex streams perfectly remotely.
I have absolutely no clue what the real cause was. If it was packet loss due to a faulty cable, i should have noticed it in the competitive games i play which require low latency and packet loss, but somehow changing the cable fixed it. I would have expected the game Counter Strike 2 to be very sensitive if there was any WAN issues.
Either way, it’s resolved now.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.