Many items not playing in chrome

Server Version#: 1.40.0.7998 (Linux Ubuntu 2.04.1)
Player Version#: 4.123.2 Plex Web (chrome 122.0.6261.112 (Official Build) (64-bit) Windows)
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>

the data is on a NAS which is mounted on /media/nas in Linux.

I changed the server 2 months ago and since then something is “broken”: some movies / TV shows episodes which I watched a month prior to the switch I can’t watch anymore.

If I watch the same from an iPad they work. I’ve today installed the Windows Plex App and in this it works too.

But in Chrome, I just get a spinning wheel and nothing happens for > 5mins (didnt wait longer)

ah, here
badger.zip (22.3 KB)

get into the “Plex Media Server” directory (under /var/lib)

make a tar.gz of the “Logs” directory.

Drag & drop it with your reply.

logs.tar.gz (5.0 MB)

I’m setting a few things but not what I’m hoping to find (no ‘smoking gun’)

  1. Please go into Settings - Server - Network - Show Advanced
  2. Turn OFF IPv6 support. Your LAN is IPv4 only. It’s messing with the devices trying to connect.
  3. SAVE that change

After the change, Please test again --HOWEVER

  1. Settings - Plex Web - Debug - Enabled
  2. Now attempt a playback which fails
  3. When it’s done,
  4. Click the ‘here’ at You can view the debug logs here.
  5. Save that to a text file (.log extension) and attach here
  6. Also download the server logs again and attach them.

Thanks.

thank you, will do when at home again.

plex20240312-1820.log (36.6 KB)
logs20240312-1821.tar.gz (5.2 MB)

same file as yesterday, didn’t work

THanks for the logs.

Did you disable the IPv4 “Lookback” (http://127.0.0.1) adapter ?
It’s not responding.

  {
    "type": "log:message",
    "level": 4,
    "message": "[Connections] Testing connection for [Loopback] at http://127.0.0.1:32400/media/providers",
    "time": "2024-03-12T17:17:42.286Z"
  },
  {
    "type": "log:message",
    "level": 4,
    "message": "[Connections] Testing legacy connection for [Loopback] at http://127.0.0.1:32400",
    "time": "2024-03-12T17:17:42.286Z"
  },
  {
    "type": "log:message",
    "level": 4,
    "message": "[Connections] Retrying connection tests for [Loopback] in 22 seconds",
    "time": "2024-03-12T17:17:42.288Z"
  },
  {
    "type": "ajax",
    "url": "http://127.0.0.1:32400/media/providers?X-Plex-Product=Plex%20Web&X-Plex-Version=4.123.2&X-Plex-Client-Identifier=0elkwgstzsa8h0wnkqm7jntb&X-Plex-Platform=Chrome&X-Plex-Platform-Version=122.0&X-Plex-Features=external-media%2Cindirect-media%2Chub-style-list&X-Plex-Model=bundled&X-Plex-Device=Windows&X-Plex-Device-Name=Chrome&X-Plex-Device-Screen-Resolution=1156x803%2C2560x1440&X-Plex-Language=en&X-Plex-Session-Id=61e65533-a170-466c-8fc9-a6a1f215d653",
    "status": 0,
    "headers": {
      "Accept-Language": "en",
      "Accept": "application/json"
    },
    "statusText": "error",
    "time": "2024-03-12T17:17:44.334Z"
  },
  {
    "type": "log:message",
    "level": 1,
    "message": "[Connections] [Loopback] is unavailable at http://127.0.0.1:32400/media/providers (Status 0)",
    "time": "2024-03-12T17:17:44.334Z"
  },

EDIT:

FYI: There was a partial Plex authentication outage for parts of Europe (some of Fance). It might be best to restart PMS and confirm the fault still exists.

if I see that correctly, that part of the log is from the client, i.e Windows PC? the Windows PC doesnt have PMS on it.
Which might be a part of the problem somehow

restarted and tried again, not working (not in France though)

Correct – The log is saying it’s trying to / thinks the server is local.

Looking at your account, I see the Ubuntu machine,

Rather than opening this via the Ubuntu server, do you see a different behavior if you open https://app.plex.tv ?

no difference unfortunately. enabled debug again, adding both kind of logs here.

so, if my Windows client thinks it should access it’s own localhost, is there anything I can do like purge some Chrome cache or something?
( I tried shortly after in a Firefox, also not working)

I can maybe try on another computer tomorrow evening; not sure if I’ve ever used plex on that one.

plex20240312-2250.log (26.6 KB)
logs20240312-2251.tar.gz (4.5 MB)

I wish I knew how to address this on Windows. I’m the Linux guy.

@FordGuy61

Have you any thoughts here?

I can ping 127.0.0.1 on the Windows PC, but I wouldn’t expect to have the plex running there on port 32400 (since plex is on the Linux server).

I have not had the spinning wheel problem with Chrome.

I have had other problems, such as the stream skipping ahead a second or two. Enabling the alternate streaming protocol (Settings + Show Advanced → Plex Web → Debug) helps with that issue.

Chrome just updated to 122.0.6261.112 on my PC. I’ll stream various media types from my servers this evening and see if I can re-create the spinning circle problem.

As far as additional troubleshooting, you should also try disabling any Chrome extensions. One might be getting in the way. You could also use an incognito window, as that should bypass any extensions or other add-ons.

FWIW, I rarely use a web browser to watch media on my PC due to browser limitations. I use Plex Desktop for Windows, as it direct plays pretty much everything. It also scales & tone maps 4K HDR media to my 1080p SDR display. It does hit the CPU a bit, but that is expected, as neither my CPU (4790K) or GPU (750Ti) support HEVC video (yeah, time for an upgrade, LOL).

I could get Chrome 122.0.6261.112 today too.
tried incognito both before and after update.

still not working. I can put logs from those tries too if you want.

only chrome extensions currently is “Volume Master” (which I had while it was working on the old server).

Unfortunately, I’m unable to recreate the problems you’re experiencing with Plex Web.

I played several movies / tv episodes and they all started within a few seconds.

1080p H.264 and 480p HEVC (8 bit) both started quickly, within 3 to 4 seconds. A couple seconds longer if PMS had to burn subtitles.

4K HDR media started within 5 to 7 seconds. I expected it would take longer, since PMS has to transcode and tonemap the video.

I’m using Chrome 64-bit on Windows 10 Pro. The PC and Plex server are wired into the same Ethernet switch. Plex Web is via app.plex.tv, currently v4.125.1.

man, sometimes. I would have sworn I had written this but it seems not? Maybe only in a local text…

It’s not with all kind of movies / tv shows:

  • xvid not working.
  • DAC audio not working.
  • MPEG4 with MP3 not working (the one in the logs)
  • H264 with AAC is working ( I think this doesn’t need any transcoding for the web client?).
    (not full list obviously)

sorry about this

I found a test AVI file online with xvid video and mp3 audio. It plays within a couple of seconds and transcodes to H.264 & AAC.

V001 AVI - MPEG-4 XVID NTSC 480p - MP32.0.avi.zip (1.1 MB)

Even though it plays, XVID is an old codec. Consider acquiring the movies/shows in a more modern version, such as H.264 or HEVC if possible. Or maybe run them through Handbrake to convert them.

I don’t have a DAC, but the web browser will not let you select which audio output to use. If this is for music, look at Plexamp or use Plex Desktop. Both let you choose the audio output.

thank you for the test movie.

not playing ;(
plex 20240313-2308.log (49.8 KB)
logs-20240313-2308.tar.gz (4.6 MB)

my best guess is that my “web profile” is borked somehow.
Where is that saved / can I reset it?

Or should I create a new plex account and try with that or something?

I do not know why the file will not play. PMS starts the transcode, but Plex Web drops the connection:
Mar 13, 2024 21:41:24.984 [140109167450936] DEBUG - [Req#bd85/Transcode] Streaming Resource: Terminated session 0x7f6dbd5d8498:am3cwnuc4pq62ftf5io5nd6s with reason Client stopped playback.


Can you try streaming from a system on the 192.168.1.x network? The PC you are using is on 192.168.13.x, and PMS is treating it like a remote connection. It should not make a difference, but it will not hurt anything to try.
Mar 12, 2024 19:54:21.924 [140109391751824] DEBUG - Detected primary interface: 192.168.1.110


Creating a new account will not make a difference. There is nothing in the account settings regarding what media types will or will not direct play, transcode, etc. If you do create another account, do not delete the account you are currently using.

I think the problem is with Chrome or a Chrome setting. However, I’ve no idea what to check. My browser is basically on default settings and the video plays OK.

You’re transcoding in software, but the I7-4770 should be able to transcode 1080p video OK. It will not transcode 4K video.

there is normally no PC or other client on the 192.168.1.* network, it’s strictly external. But I guess I could my laptop to that network, lets see

network setup
providerAP (192.168.1.1) ↔ serverExt(192.68.1.110) on same pc as serverInt(192.168.13.3) ↔ normalClient(192.168.13.*).

(ifconfig on the server shows the internal network first)
(this was the same basic structure on the old server but the “order” of the network interfaces might have been different).

test on laptop connected to external:
ip 192.168.1.113 (LAN not WLAN)
connected to 192.168.1.110:32400, turned on debug in the settings, but changed nothing else.
Clicked the movie you linked yesterday → spinning. After ~30s it went back to the movie list (this is new behavior but might be related to the short length of the movie?) tried again, same.

Regarding Chrome: the same happens also on Firefix; I don’t think I’ve tried Edge but could try to narrow it down or install another browser.

logs-20240314-1138.tar.gz (4.6 MB)
laptop plex20240314-1138.log (78.9 KB)