Remote access shows all files missing, but present locally

Server Version#: 1.29.2.6364
Player Version#: 4.94.2

I’ve been running a Plex server on a succession of Mac Minis for many years. I just migrated the server to new hardware (a new Mac Mini) and have encountered this odd problem:

When I open the Plex web player LOCALLY (that is, on the Mac Mini which is acting as the server), everything functions correctly. I can see my libraries and play content.

When I open any REMOTE player (Plex or PlexAmp on Android or iOS, web player, smart TV app) either on the same LAN or somewhere else, I can see all my libraries, but when I click “play” on any movie or song, I get the error “Please check that the file exists and the necessary drive is mounted.”

I can walk over to the server and play the file just fine, and immediately walk back to any other machine and the file is ‘missing’.

All the content is stored a Drobo 5C (not a NAS, just an external storage device) which is connected directly to the Mac Mini by USB-C. The Mac Mini has an ethernet connection directly to a switch which is connected in turn to my router, a Netgear Orbi, and from there to the Verizon Fios box.

Everything I can think to check has current OS / software versions (Drobo, Mac OS, Android, Chrome, Plex server and player, etc). I’m sure I’m missing something, so I’m grateful for any advice! Let me know what logs or details I can provide.

With Fios it’s probably their router and/or dns rebinding.
Use their mobil app to disable Home Network Protection and retest.
Any luck? Here’s some background info in a tiny font to help your coffee disappear.

You can find a few other topics about Fios on the forums.

In case anyone is finding this post in the future: I tried playing my usual test movie from one client, and it still didn’t work. Then I tried playing a movie I had not played before from that same client, and that worked perfectly. I went back to my test movie, and now it worked, and it also worked from every other client.

I don’t understand how that resolved the problem, but the problem appears to be fixed.

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