ipv6 was the culprit for me
Just wanna let you know that disabling the IPV6 on my nic also fixed my issue with metadata downloading. It for some reason also fixed metadata downloading for Calibre (My Ebook Software) when downloading metadata there too. Freaking weird.
South Dakota, Vast Broadband
I was having this issue where no posters or background images would download and tried disabling IPV6 but what worked for me was deleting the cashe folder for TMDB. after that I it worked fine.
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!
Any updates on this? I just had to disable IPv6 on the box. Seems like a maladroit solution to say the least.
Same problem here, either with a windows and linux pms. It seems the problem is Plex pulling pictures from the movie database.
The TV Database works fine.
@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 cardWill 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 annoyingIf 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 networkWould 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/Xfinitydisabling 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
Iām sorry, but the āOUR software has a problem, YOU fix itā approach doesnāt seem very professional to me (Iām aware curl is not your software, but it still is a tool your software uses).
So, isnāt there a way for Plex to avoid this issue? A fallback to ipv4 if ipv6 fails doesnāt sound impossibleā¦
@Nozavi said:
Iām sorry, but the āOUR software has a problem, YOU fix itā approach doesnāt seem very professional to me (Iām aware curl is not your software, but it still is a tool your software uses).So, isnāt there a way for Plex to avoid this issue? A fallback to ipv4 if ipv6 fails doesnāt sound impossibleā¦
It is falling back to ipv4 after trying out the list of ip addresses in sequence - but that slows down the process immensely as a backlog builds up as the ipv6 connections are not failing immediately but getting timed out
If ipv6 is not fully functional on your system, what is the objection to disabling it on the network card
@sa2000 said:
@Nozavi said:
Iām sorry, but the āOUR software has a problem, YOU fix itā approach doesnāt seem very professional to me (Iām aware curl is not your software, but it still is a tool your software uses).So, isnāt there a way for Plex to avoid this issue? A fallback to ipv4 if ipv6 fails doesnāt sound impossibleā¦
It is falling back to ipv4 after trying out the list of ip addresses in sequence - but that slows down the process immensely as a backlog builds up as the ipv6 connections are not failing immediately but getting timed out
If ipv6 is not fully functional on your system what is the objection to disabling it on the network card
Also ipv6 does actually work for other users for retrieving these images.
Extensive tests were done here https://forums.plex.tv/discussion/comment/1609469/#Comment_1609469 by @benbreton and I believe the issue arises when the ISP does not provide full IPv6 support
@Nozavi said:
Iām sorry, but the āOUR software has a problem, YOU fix itā approach doesnāt seem very professional to me (Iām aware curl is not your software, but it still is a tool your software uses).
The issue is not in curl
Curl.exe is just a tool you can use to troubleshoot your ipv6 functionality
What i was saying is that users with this issue - where it is confirmed as being the issue (i.e. resolved by disabling ipv6 on the network card) should look into their ipv6 to establish why it is not getting through to an ipv6 IP address. It could be an ISP issue
@sa2000 said:
It is falling back to ipv4 after trying out the list of ip addresses in sequence - but that slows down the process immensely as a backlog builds up as the ipv6 connections are not failing immediately but getting timed out
But thereās a difference you see between getting to the ipv4 IPs in time and not reaching them AT ALLā¦ I know this is the movies thread, but Iāve obviously had the same problem with TV shows and I had episodes or entire seasons not processed AT ALL because of this bugā¦ I had to resort to finding weird workarounds to fix these problems because that backlog you mention doesnāt always work and sometimes files remain unprocessed. By the way (considering thereās an obvious difference between v6 and v4 IPs) why arenāt they just skipped if āEnable server support for IPv6ā is disabled in the serverās settings?
If ipv6 is not fully functional on your system, what is the objection to disabling it on the network card
What i was saying is that users with this issue - where it is confirmed as being the issue (i.e. resolved by disabling ipv6 on the network card) should look into their ipv6 to establish why it is not getting through to an ipv6 IP address. It could be an ISP issue
The objection is that thereās a problem with the way Plex works and you expect users to fix it.
You expect users who most probably DONāT KNOW thereās a problem with Plex to:
- notice a pattern, investigate and discover a bug
- find the Plex forums and this specific topic
- without ANY knowledge on your part regarding their IT knowledge, their home network and their ISP, to either make changes to their network configuration or contact their ISP with a very specific, yet complex matter
And you insist this is all absolutely normal :))) I dare you to go out of your bubble and ask around, see how many people have EVER:
- heard of IPv6 and what it is/means (let alone have an entire conversation or troubleshoot it with someone)
- contacted their ISP (at least for anything other than āmy facebook is not workingā)
- made any changes to their network configuration (at least anything other than entering their DHCP/PPOE info)
In case you havenāt noticed, Plex is not some niche software used exclusively by IT experts, so stop assuming everyone can handle these bugs/fixes. Last, but not least, I stand by my initial statement: it should be up to YOU, Plex, to find a solution or at least a workaround for this problem, not the users (not to mention how that solution might sound to inexperienced people).
PS: Am I the only one who thinks the community would be a lot happier and larger if Plex would focus on fixing bugs as much as it does on releasing new features? For months Iāve been having problems with subtitles, Plex on Android, DVR, Plex on Kodi, there have been so many complaints here (not to mention Reddit) and yet nothing, bugs are still thereā¦ for months and months! But hey, at least weāve got Plex for Alexa in India! Jeeeeeeeez
1 Like
Iām having this problem and IPv6 is not, and has never been enabled on my server machine.
@davel23 said:
Iām having this problem and IPv6 is not, and has never been enabled on my server machine.
which problem ? The 100 second delay / timeouts.
If it is not ipv6 related - then it needs to be raised as separate forum topic with logs and details of what is failing
@sa2000 said:
@davel23 said:
Iām having this problem and IPv6 is not, and has never been enabled on my server machine.which problem ? The 100 second delay / timeouts.
If it is not ipv6 related - then it needs to be raised as separate forum topic with logs and details of what is failing
Iām having this very same problem but it is not related to IPv6.
Iāve opened this post with all the logs attached. Still waiting for someone to take a look at the logs.
Thereās is a lot of people out there having issues with TMDb artwork.
https://forums.plex.tv/discussion/316062/problem-downloading-artwork-from-tmdb#latest
Looking at ādevelopers.themoviedb.orgā, I found that there are many problems with āCloudflareā and the TMDB API, like these:
https://www.themoviedb.org/talk/58c6b683c3a36841200172d8
Help with something?
@Enderin said:
Looking at ādevelopers.themoviedb.orgā, I found that there are many problems with āCloudflareā and the TMDB API, like these:API rejecting plugin user-agent - Talk ā The Movie Database (TMDB)
Help with something?
I was looking for rate limiting responses and indication but the wireshark captures did not show any - I will have another look
This relates to the investigations here https://forums.plex.tv/discussion/316062/problem-downloading-artwork-from-tmdb/
The ipv6 issues are separate
@sa2000 said:
@TeflonDon said:
I now have this problem. Started 3 days ago. I have disabled ipv6 everywhere with no joyHelp pls. Logs attached
I am going to move your post into a new forum topic. You have already stated that you disabled ipv6 - so it is clear that this topic is not relevant to you as the title states that the issue in this forum thread is to do with ipv6
Ok. Pls let me know the link sir
I am using IPv6 with ULA-prefix internally, with no default route for IPv6 because my ISP do not provide IPv6 yet. This is a totally valid scenario, and since there are no IPv6 default route, there is never a reason for trying to use IPv6 to access internet addresses. This is a plex bug. It is the only malfunctioning service in my network with IPv6.
@marsboer said:
I am using IPv6 with ULA-prefix internally, with no default route for IPv6 because my ISP do not provide IPv6 yet. This is a totally valid scenario, and since there are no IPv6 default route, there is never a reason for trying to use IPv6 to access internet addresses. This is a plex bug. It is the only malfunctioning service in my network with IPv6.
I have not seen any diagnostics from you and I do not know if you have the 100 second delay issue caused by attempting to use ipv6 IP addresses for image.tmdb.org
