The logs give a hint of the issue we have seen before when the ipv6 routes to image.tmdb.org are not reachable
you can do some testing using curl.exe for specific url’s eg
http://image.tmdb.org/t/p/w300/jXtKhWFg3ykUMABl6iZuJs9B462.jpg
and time them
Logs show 100 seconds+ before images are returned
See these examples
2019-01-29 23:11:36,078 (34a0) : DEBUG (networking:166) - Requesting 'http://image.tmdb.org/t/p/w300/jXtKhWFg3ykUMABl6iZuJs9B462.jpg'
2019-01-29 23:13:16,302 (34a0) : DEBUG (networking:198) - Not caching 'http://image.tmdb.org/t/p/w300/jXtKhWFg3ykUMABl6iZuJs9B462.jpg' (content type 'image/jpeg' not cacheable in Agent plug-ins)
and
2019-01-29 23:13:16,311 (34a0) : DEBUG (networking:166) - Requesting 'http://image.tmdb.org/t/p/w300/5vZw7ltCKI0JiOYTtRxaIC3DX0e.jpg'
2019-01-29 23:14:56,365 (34a0) : DEBUG (networking:198) - Not caching 'http://image.tmdb.org/t/p/w300/5vZw7ltCKI0JiOYTtRxaIC3DX0e.jpg' (content type 'image/jpeg' not cacheable in Agent plug-ins)
2019-01-29 23:14:56,371 (34a0) : DEBUG (networking:166) - Requesting 'http://image.tmdb.org/t/p/w300/tfhJDGI8uyMlUVjGQ61iW4WNnPb.jpg'
2019-01-29 23:16:36,424 (34a0) : DEBUG (networking:198) - Not caching 'http://image.tmdb.org/t/p/w300/tfhJDGI8uyMlUVjGQ61iW4WNnPb.jpg' (content type 'image/jpeg' not cacheable in Agent plug-ins)
and so on
And with an overhead of 100 second + for each image, the overall request to the agent to get metadata times out after 10 minutes
Jan 29, 2019 23:11:26.288 [25340] DEBUG - HTTP requesting GET http://127.0.0.1:54136/:/plugins/com.plexapp.agents.imdb/messaging/function/X0FnZW50S2l0OlVwZGF0ZU1ldGFkYXRh/Y2VyZWFsMQoxCmxpc3QKMApyMAo_/Y2VyZWFsMQoxCmRpY3QKMTAKczIKZW5zNApsYW5nYjFzNQpmb3JjZWIwczgKcGVyaW9kaWNzMgozOXM0CmRiaWRpMApzNwp2ZXJzaW9ubnMxMApwYXJlbnRHVUlEbnM4CnBhcmVudElEczUKTW92aWVzMTAKbWVkaWFfdHlwZXM0Mwpjb20ucGxleGFwcC5hZ2VudHMuaW1kYjovL3R0MDE3MjQ5NT9sYW5nPWVuczQKZ3VpZHM5CnR0MDE3MjQ5NXMyCmlkcjAK
Jan 29, 2019 23:21:26.602 [25340] ERROR - Error issuing curl_easy_perform(handle): 28
Jan 29, 2019 23:21:26.602 [25340] DEBUG - HTTP simulating 408 after curl timeout
Jan 29, 2019 23:21:26.602 [25340] DEBUG - [com.plexapp.agents.imdb] HTTP reply status 408, with 0 bytes of content.
It may be that your ISP DNS is returning ipv6 addresses and yet unable to reach some ipv6 sites
nslookup image.tmdb.org will probably show 5 ipv6 addresses and 5 ipv4 addresses. The 100 second dekay arises when trying out each of the ipv6 routes with a 20 second timeout on each.
The issue was investigated on this forum thread
You could try to disable ipv6 in the router - or get your isp to look into why image.tmdb.org is not reachable through the 5 ipv6 addresses
Note that the ipv6 setting within Plex Media Server Network Settings does not have any impact on how outward connections are made
