Server Version#: 1.25.2.5319
Player Version#: —
Android App Version#: 8.27.2.29938 (834096929)
I recently reinstalled Plex. Metadata, transcoding and playback is working without any issues. But all client apps (Fire TV, Apple TV, Android, iOS) never display any images (covers, profiles, …).
The webplayer however is always working, everything is showing up there.
PMS installed in a Proxmox Arch Linux LXC / Remote Access using HAProxy + Let’s Encrypt
I just checked the client logs and they don’t indicate any errors.
Is there anything I can do on the PMS to find the issue?
Bump.
Bump.
I find it kinda strange that there is no real support for problems here. No offense.
Bump. Again…
Bump.
Do the issues go away if you remove these variables, connecting Plex directly? It would be a useful troubleshooting step.
Nope they persist.
I also can’t think of any reason why it could have something to do with the reverse proxys since the web player is working without any issues. Unless the client apps use some very special way of accessing the Plex server.
But then again the only thing that changed was the reinstallation of Plex. So I don’t think it is related to the reverse proxy.
I wonder if the lack of covers/images could be a permissions issue.
Plex renders a version of the poster that’s sized appropriately for each request, and caches the files on disk.
Can you share server logs?
See below a server log during an access of a client app.
I also attached the file system structure, it doesn’t indicate any permission issues.
pms_server.txt (48.0 KB)
permissions.txt (4.4 MB)
I agree the permissions look fine.
Jan 17, 2022 20:05:20.904 [0x7f13c5032b38] WARN - HTTP error requesting GET http://127.0.0.1:80/library/metadata/2/thumb/1640135042 (7, Couldn't connect to server) (Failed to connect to 127.0.0.1 port 80: Connection refused)
Plex makes an HTTP API call to itself for the thumbnails and images, but it always (I think) uses port :32400 to do so. And Plex doesn’t ever (I think) listen on :80.
Is this traffic firewalled/translated/mapped/hijacked in some way?
I’m confused by the log! It looks like Plex itself is making the request to http://127.0.0.1:80/.... That’s weird. I expect to see http://127.0.0.1:32400/....
Are you sure it works if you disable the HAProxy stuff? I’m wondering if there’s some funky interaction with X-Forwarded-Whatever or other headers.
Oh man. This is so stupid… I found the error.
I had set the local IP of the Plex server in Network --> Custom server access URLs like http://192.168.2.5,https://192.168.2.5.
Removing it fixed the issue.
Oh! I’m glad you figured it out.
That’s bizarre. That field is supposed to register additional URLs with the Plex Cloud for server discovery. I don’t think it’s supposed to change how these loopback requests behave. Requests going to :80 is just weird.
But I’ve noticed Custom server access URLs behaves strangely if the server’s local IP addresses are entered, even with different ports → they get dropped completely. This sounds similar!
The reason it was trying to access port 80 was because I had the http URL set.
Just to clarify one SHOULD NOT place the local ip in the custom access URLs right?
Network --> Custom server access URLs
https://plex.yourdomain.com,http://192.168.2.5,https://192.168.2.5
→ This is wrong?
Network --> Custom server access URLs
https://plex.yourdomain.com
→ This is correct?
To my knowledge, it always publishes the server’s natural LAN IP address for client discovery.
I’m pretty sure addresses are registered like this:
Custom server access URLs entries, ordered randomly
Remote Access is enabledThis is useful - you can see what’s been registered with Plex:
https://plex.tv/api/resources?includeHttps=1&X-Plex-Token=TOKEN
FWIW, I’m trying various things in Custom server access URLs and can’t duplicate the behavior (requests sent to 127.0.0.1:80) that you were experiencing.
No worries, since it’s working for you now. 
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
