Metadata no longer being applied to Movies (confirmed as ipv6 timeout delays)

Plex Media Server Desktops & Laptops
67

@nperron said:
I’m assuming this bug will be corrected on the next update ? very annoying

@Nozavi said:

@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.

@afh414 said:

@sa2000 said:

@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

Is this a joke? This is your solution?!?

@“Wrecking Ball” said:

@sa2000 said:
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

Territory - USA
ISP - Comcast/Xfinity

disabling ipv6 on my network adapter worked for me too. very frustrating issue, just glad someone figured out a temporary fix.

@afh414 said:
Are we thinking this fix is on the 2018 or 2019 roadmap? Just curious…

@marsboer said:
For God’s sake, how can this not have been fixed after several months!?!?
Disabling IPv6 is not acceptable even as a workaround in 2018! This should have been fixed in days, not months!

@realmz41 said:
Any updates on this? I just had to disable IPv6 on the box. Seems like a maladroit solution to say the least.

Have been doing more tests on this and it does work ok through ipv6 for some users but does not for others.

There is not actually a bug here in Plex Media Server. Plex Media Server is connecting to the image.tmdb.org site through the routes it finds in DNS and for some of you the ipv6 connections are not working.

image.tmdb.org resolves to these 10 IP addresses

Name:    image.tmdb.org
Addresses:  2400:cb00:2048:1::6810:3a9b
          2400:cb00:2048:1::6810:3b9b
          2400:cb00:2048:1::6810:399b
          2400:cb00:2048:1::6810:3c9b
          2400:cb00:2048:1::6810:3d9b
          104.16.57.155
          104.16.59.155
          104.16.58.155
          104.16.61.155
          104.16.60.155

So for those of you who are not prepared to disable ipv6 on the network card, could you look into getting ipv6 to actually work on your system and through your ISP.

The problem arises when the connections to the five ipv6 addresses time out. They should not time out if your ipv6 is working correctly

You can do this simple test in a command line session using curl which you can download from curl - Download

curl -v6o junk.jpg "http://image.tmdb.org/t/p/w300/g8wnyyR6vlZjfdePD2v1lKGLUix.jpg"
This will test out your ipv6 route to image.tmdb.org and fetch an image using ipv6 and save it into file junk.jpg

If it fails then it means your ipv6 is not working and if it does not work with all web sites, then you migth as well disable it on the network card