Wondering if you have ant TCP Optimization software or bandwidth management software installed on your server computer
No bandwidth management or TCP Optimization software installed at all. PM sent with dropbox link to files requested.
@sdownes said:
No bandwidth management or TCP Optimization software installed at all. PM sent with dropbox link to files requested.
Thank you for the procmon capture and logs and wireshark - very very useful
The wireshark confirmed the 100 second delay before the requests went out
The procmon capture showed what the problem is
The images.tmdb.org is resolving to both ipv4 and ipv6 addresses
and you have ipv6 enabled within Plex Media Server Network settings
The proc mon shows it tried to get through with ipv6 and after a number of tries (5 x 20 second timeouts) switched to ipv4
So disable ipv6 in network settings in server settings and see how it goes
Please look into disabling ipv6 within the network. I am discussing this with the development team
I am hoping that by eliminated that 100 second wasted time on ipv6 reconnection attempts to image.tmdb.org that the issue with metadata will be resolved
If not, you know what to do ā¦ diagnostics
If it is already disabled in Plex Media Server then it is windows that must be using ipv6
Please let me know what the setting is now
There could be an issue with the python Plex processes - may be not checking server ipv6 setting
I took this thread and tested a theory, I had also been having issues with the movie meta data downloading, it was working a few weeks back on my new win 10 plex VM but quit working in last few days. I had cleared caches, updated, fresh installed, fresh installed an old version 1.9.7.4460, uninstalled my AV, disabled windows FW, NOTHING made any difference; Metadata for movies just did not download. TV and Music were fine. IPv6 was disabled in my plex as mentioned above and still no change. SInce IPv6 was mentioned I took a flyer and disabled IPv6 on my nic in adapter properties and suddenly everything was working and metadata is flying in. It would seem that ipv6 is certainly part of the issue for me.
@drucius said:
I took this thread and tested a theory, I had also been having issues with the movie meta data downloading, it was working a few weeks back on my new win 10 plex VM but quit working in last few days. I had cleared caches, updated, fresh installed, fresh installed an old version 1.9.7.4460, uninstalled my AV, disabled windows FW, NOTHING made any difference; Metadata for movies just did not download. TV and Music were fine. IPv6 was disabled in my plex as mentioned above and still no change. SInce IPv6 was mentioned I took a flyer and disabled IPv6 on my nic in adapter properties and suddenly everything was working and metadata is flying in. It would seem that ipv6 is certainly part of the issue for me.
Iām having the exact same problem here as well.
IPv6 is also disabled in Plex.
Where did you disable IPv6 to get Plex running again? (nic?)
I have amended my earlier response. It appears that the metadata agents networking code is not checking the Plex Media Serverās ipv6 setting. I will discuss this with the development team.
Until there is a change to Plex Media Server agents networking, if ipv6 is the cause of your issues, please look into disabling ipv6 protocol for the computer / device running Plex Media Server
Got it all sorted now!
Disabled IPv6 on my network card and forced refresh of metadata on the server - itās now downloading the metadata.
Looks like disabling IPv6 on the properties of my ethernet adaptor worked for me too! Thanks for all the help.
This worked for me too(disabling ipv6 on nic). Really glad someone figured it out, as there are many posts about this issue. If it is not already, this should be stickied somewhere.
would like to establish why the availability of ipv6 ip addresses for image.tmdb.org is impacting some users but not others when ipv6 is in use on the network
Would like each person who has confirmed that it was ipv6 that was affecting metadata / images being fetched to let me know
- the location of the server (territory)
- what ISP is the connection through
@sa2000 said:
- the location of the server (territory)
- what ISP is the connection through
My server is located in Norway. ISP is Telenor Fiber
ND, USA. Midcontinent Communications
Chicago area, Illinois. Comcast
Iām assuming this bug will be corrected on the next update ? very annoying
@nperron said:
Iām assuming this bug will be corrected on the next update ? very annoying
If ipv6 is causing timeouts on metadata requests for images, please disable it on the network card
Hope this helpsā¦
I had same problem. When I changed my Asus Router on itās IPv6 config from DHCP to Auto-detect, rebooted router and server, it started working again.
My ISP is Spectrum (formally TWC).
@sa2000 said:
If ipv6 is causing timeouts on metadata requests for images, please disable it on the network card
Will this ipv6 bug EVER be fixed? Itās causing so many problems and asking people to change their network configuration (which btw isnāt that easy to do on some routers and servers) because one piece of software isnāt compatible with it to me seems VERY unprofessional.
