Server Version#: 1.25.4.5468
Player Version#: 8.29.0.30433 (b377acd)
plex-401-404-error-troubleshooting-android.txt (9.5 KB) plex-401-404-error-troubleshooting-windows.txt (6.7 KB)
Hello, I’m running into an interesting issue. On the same Plex server, Android clients are unable to load media art while Windows & web clients load art just fine. Other metadata loads OK on Android; while checking logs, I noticed several 401 and 404 errors. This behavior is consistent with all Android clients I have tested with (Android 12 on my Pixel 6 Pro, Android 11 on my Nvidia Shields). There are no similar 401/404 messages for requests from the Windows / web clients.
I have attached two files containing server logs generated while (1) loading a movie page on the Android client (with 401 and 404s) and (2) loading the same movie page from the Windows client. Both the Android and Windows client are on the same subnet in relation to the Plex server. If more info is needed, I can share. Appreciate any help!
The Windows client is sending an https request. The Android app is sending an http request. I don’t know why it’s sending an http request or why it is failing. Other http requests seem to be fine.
Can you provide the log from one of your Android devices?
Sorry for the long delay. I didn’t have a chance to grab my logs before traveling last week, but I’m home now and can pick this back up.
I’m not sure why this would make a difference, but in case context is helpful, I’m running two PMSs on TrueNAS Scale via TrueCharts. The primary PMS behaves entirely as expected in the Android app, it’s only the secondary PMS that is exhibiting this issue. As the two PMSs are on the same physical host, the secondary PMS is using a non-standard port (32402). Outside of that, they’re more or less configured in the same way. Everything else with this secondary PMS seems to work great, it’s (seemlingly) just the posters that don’t load on Android. I have tried redeploying the PMS, starting a new DB from scratch, etc., but I can’t seem to get it working.
Wow, thank you!!! I must have just missed that thread when I researching this issue prior to making this thread (I was researching a couple days prior to posting).
In any case, as noted in the linked thread, removing the IP address from Custom server access URLs 100% solved my issue. Previously, I had https://my.reverse.proxy.address2,https://IP:32402. After removing https://IP:32402, the Android client seems to be working fine again.
Note, having https://IP:port only seems to be an issue when non-standard ports are in use. My primary PMS still has https://my.reverse.proxy.address,https://IP:32400 and has had no issues…though I’ll probably remove it.
I unmarked the above post as the solution, as this actually this then creates a new problem. Removing the IP address entry then causes the PMS to be detected as Remote rather than Nearby. This is despite both my Kubernetes and LAN supernets being listed under LAN Networks. For the time being, I’d much rather have the metadata artwork than my PMS location being properly detected, but this is definitely an issue.
Ok. You can’t use https addresses under the custom access url unless you have provided your own security certificate, otherwise there is no way no make a secure connection. Plex’s provided certificate only works with Plex’s plex.direct address. To use these addresses, just use http and then make sure the client is set to always allow insecure connections.
Ah, OK that makes sense–thanks for the explanation! I have a cert on my reverse proxy, but not in the Plex app itself. I’ll give your suggestion try; assuming that works, I should be able to generate a cert, install it in Plex directly, then be able to use HTTPS?
