Plex on Ubuntu buffering on remote

Server Version#: 1.40.2.8395
Player Version#: Version 1.91.0.129-1cd63c1d also tried on Chrome via a MAC and on a Windows laptop Chrome
Plex Media Server Logs_2024-05-02_21-17-34.zip (5.3 MB)

Hello everyone,

This is my first post on the forum as I ran out of solutions.

So I had a buffering problem with my Synology hosted Plex, each time I was away (I travel a lot) I had buffering issues.
Long story short I understood that I need to move Plex to a dedicated machine, so I moved it on a sitting laptop with AMD Ryzen 5 4600H, 16GB on RAM and a 1650GTX with SMB to the Synology where I keep my movies and got myself a Plex pass.
It didn’t help with much, I still get the buffering situation, wherever I am remotely, even thou I tried different internet lines ( almost all of them 50mbps +) .
My home network is fully gigabit and I got 1gig internet line.

Please help!

What information is showing in the “now playing” tile for that playback on the Plex server dashboard?
Specifically:

  • is the steam listed as remote or indirect?
  • are any parts of the stream transcoded?

Exemplary screenshot from the "now playing" section
https://support.plex.tv/articles/200871837-status-and-dashboard/

This is what I am getting while checking now on a remote connection.
I didn’t understand the 2nd connection, how can I check?

That’s looking ok.
What is the internet upload speed at your home (connecting your home internet to the internet)?

I got fiber optic in the house, I usually get over 500 mbps up/down.

This is a test from tonight.

That should leave enough headroom for a 40-50 Mbps stream. I take it there’s also no bottleneck on the remote location from where you’ve been streaming?

I cannot currently check your server logs… maybe there’s something else we’re missing.

There is nobody at home, only my PC turned on, NAS and laptop hosting plex. I use Unifi dream machine as a router and a unifi switch to hookup the rest of the devices via 1gbps ports.

I attached the logs in the first post, are they broken or something?

I suppose they’re fine… but I’m out and only on my mobile.

1 Like

Would the hardware specs do? Should I be looking to upgrade?

We need the server’s DEBUG logs ZIP file of it happening so we can see what is causing it.

Specs only tell us what it can do in the best case scenario not what’s currently happening and why.

I found your logs (my apologies)

My first recommendation is : Turn off IPv6 support (Settings - Server - Network)
You have an IPv4 LAN.

May 02, 2024 06:32:00.244 [140262042667832] DEBUG - Request: [118.193.72.187:40340 (WAN)] GET /robots.txt (5 live) #37c19 TLS GZIP Signed-in
May 02, 2024 06:32:00.244 [140262042667832] DEBUG - Completed: [118.193.72.187:40340] 401 GET /robots.txt (5 live) #37c19 TLS GZIP 0ms 357 bytes
May 02, 2024 06:32:01.723 [140262042667832] DEBUG - Request: [118.193.72.187:40344 (WAN)] GET /sitemap.xml (5 live) #37c1b TLS GZIP Signed-in
May 02, 2024 06:32:01.723 [140262042667832] DEBUG - Completed: [118.193.72.187:40344] 401 GET /sitemap.xml (5 live) #37c1b TLS GZIP 0ms 357 bytes
May 02, 2024 06:32:03.194 [140262040558392] DEBUG - CERT: incomplete TLS handshake from [::ffff:118.193.72.187]:40356: Connection reset by peer
May 02, 2024 06:32:03.894 [140262042667832] DEBUG - CERT: incomplete TLS handshake from [::ffff:118.193.72.187]:40368: Connection reset by peer
May 02, 2024 06:32:04.620 [140262040558392] DEBUG - CERT: incomplete TLS handshake from [::ffff:118.193.72.187]:36266: Connection reset by peer
May 02, 2024 06:32:05.327 [140262042667832] DEBUG - CERT: incomplete TLS handshake from [::ffff:118.193.72.187]:36268: Connection reset by peer
May 02, 2024 06:32:05.997 [140262040558392] DEBUG - CERT: incomplete TLS handshake from [::ffff:118.193.72.187]:36282: Connection reset by peer
May 02, 2024 06:32:06.347 [140262042667832] DEBUG - CERT: incomplete TLS handshake from [::ffff:118.193.72.187]:36292: unsupported protocol (SSL routines)
May 02, 2024 06:32:07.434 [140262042667832] DEBUG - CERT: incomplete TLS handshake from [::ffff:118.193.72.187]:36298: Connection reset by peer
May 02, 2024 06:32:08.189 [140262040558392] DEBUG - CERT: incomplete TLS handshake from [::ffff:118.193.72.187]:36306: Connection reset by peer
May 02, 2024 06:32:08.517 [140262040558392] DEBUG - CERT: incomplete TLS handshake from [::ffff:118.193.72.187]:36316: no shared cipher (SSL routines)
May 02, 2024 06:32:09.209 [140262040558392] DEBUG - CERT: incomplete TLS handshake from [::ffff:118.193.72.187]:36324: bad key share (SSL routines)
May 02, 2024 06:33:45.056 [140261831891768] DEBUG - [Req#1fccc/ViewStateSync] Starting
May 02, 2024 06:33:45.056 [140261831891768] DEBUG - [Req#1fccc/ViewStateSync] Fetching user 

The player / remote is what’s resetting or dropping the connection.

How fast is this connection? How fast can you read from the NAS?
(use the ‘dd’ command and add status=progress to monitor reading from the NAS with writing to /dev/null)

May 02, 2024 06:51:59.305 [140262017882936] DEBUG - Activity: updated activity 1c58d73e-b8df-4930-9261-a3fe2ec2a74e - completed 71.8% - Scanning TV Shows
May 02, 2024 06:51:59.305 [140262017882936] DEBUG - Scanner: Processing directory /mnt/smb/Synology/Shows/Las Fierbinti/Las.Fierbinti.S23.1080p.WEB-DL.AAC2.0.H.264-playWEB (parent: yes)
May 02, 2024 06:51:59.312 [140262017882936] DEBUG - Skipping over directory 'Las Fierbinti/Las.Fierbinti.S23.1080p.WEB-DL.AAC2.0.H.264-playWEB', as nothing has changed; removing 32 media items from map.

NOTE: If your NAS has NFS (linux native) capability, you will be far better served than using SMB

1 Like

Unfortunately I am not at the location from which those logs were, but I had a “stable” 35-45mbps.

Meanwhile I disabled the IPV6 support I mounted the storage as NFS and in a couple of days I’ll be away from home and I can test.

Thank you,

Hello,

Solution to this situation was the protocol that I was using.
I move everything from SMB to NFS and everything is clear as daylight.

Thank you so much for your input, I really appreciate the help.

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