May be if you make 10 or so requests in parallel there would be issues
eg batch file firing perhaps 10 different requests like these in parallel
start cmd /k curl -vo junk1a.jpg "http://image.tmdb.org/t/p/original/rgNYcYmUmZSK5Ibl78NV3QT1dFV.jpg"
start cmd /k curl -vo junk1b.jpg "http://image.tmdb.org/t/p/original/rgNYcYmUmZSK5Ibl78NV3QT1dFV.jpg"
start cmd /k curl -vo junk1c.jpg "http://image.tmdb.org/t/p/original/rgNYcYmUmZSK5Ibl78NV3QT1dFV.jpg"
I canât believe it. After everything I did it turns out the problem is between the ISP/Plex/Themoviedb
I tried refreshing all metadata using a LTE modem, and it worked fine.
@âMaximiliano Fernandezâ
Have a look at your wireshark to compare a sequence for a request that terminates ok with an HTTP OK 200 response and one that does not and see if it is the same as what was in wireshark from @gonse
See http://forums.plex.tv/discussion/comment/1653848/#Comment_1653848
Remove your http filter and replace with a filter for the source port for the GET request - eg port == 11166 in the example I had (that would pick all packets with either source port or destination port equals 11166
Same issue. Live in Argentina, using Fibertel/Cablevision, and itâs impossible to fetch metadata. Timed out requests over and over againâŠ
I donât have a wifi adapter in this computer so canât test with an LTE connection. But what about a proxy? That should work, but when I enable a proxy on Windows settings I get lots of âHTTPError: HTTP Error 403: Target service not allowedâ in my PMS log.
@sa2000, there has to be a way to make this work and bypass Fibertel!
Alright, I tried the LTE connection via Bluetooth and can confirm fetching metadata works. However, this isnât feasible for maintaining the entire library. We really need a solution for Argentina, Fibertel is the largest ISP!
@AgustinCordes said:
Same issue. Live in Argentina, using Fibertel/Cablevision, and itâs impossible to fetch metadata. Timed out requests over and over againâŠI donât have a wifi adapter in this computer so canât test with an LTE connection. But what about a proxy? That should work, but when I enable a proxy on Windows settings I get lots of âHTTPError: HTTP Error 403: Target service not allowedâ in my PMS log.
@sa2000, there has to be a way to make this work and bypass Fibertel!
I have discussed with our operations team and I am afraid this between the ISP and Cloudflare / tmdb
The cloudflare is for tmdb and not one arranged by Plex - any issue probably best to raise with the ISP in first instance
@sa2000 said:
@AgustinCordes said:
Same issue. Live in Argentina, using Fibertel/Cablevision, and itâs impossible to fetch metadata. Timed out requests over and over againâŠI donât have a wifi adapter in this computer so canât test with an LTE connection. But what about a proxy? That should work, but when I enable a proxy on Windows settings I get lots of âHTTPError: HTTP Error 403: Target service not allowedâ in my PMS log.
@sa2000, there has to be a way to make this work and bypass Fibertel!
I have discussed with our operations team and I am afraid this between the ISP and Cloudflare / tmdb
The cloudflare is for tmdb and not one arranged by Plex - any issue probably best to raise with the ISP in first instance
What about the proxy solution, @sa2000? It does improve fetching metadata, but it raises other problems. For example, when a proxy is enabled, the server isnât found when I browse app.plex.tv â it does if I login via localhost 127.0.0.1:32400.
However, something else fails because of the repeated Target service not allowed errors. Iâm assuming my PMS canât be accessed from the outside when a proxy is enforced. Any ideas?
@AgustinCordes said:
Same issue. Live in Argentina, using Fibertel/Cablevision, and itâs impossible to fetch metadata. Timed out requests over and over againâŠI donât have a wifi adapter in this computer so canât test with an LTE connection. But what about a proxy? That should work, but when I enable a proxy on Windows settings I get lots of âHTTPError: HTTP Error 403: Target service not allowedâ in my PMS log.
@sa2000, there has to be a way to make this work and bypass Fibertel!
@AgustinCordes said:
@sa2000 said:
@AgustinCordes said:
Same issue. Live in Argentina, using Fibertel/Cablevision, and itâs impossible to fetch metadata. Timed out requests over and over againâŠI donât have a wifi adapter in this computer so canât test with an LTE connection. But what about a proxy? That should work, but when I enable a proxy on Windows settings I get lots of âHTTPError: HTTP Error 403: Target service not allowedâ in my PMS log.
@sa2000, there has to be a way to make this work and bypass Fibertel!
I have discussed with our operations team and I am afraid this between the ISP and Cloudflare / tmdb
The cloudflare is for tmdb and not one arranged by Plex - any issue probably best to raise with the ISP in first instance
What about the proxy solution, @sa2000? It does improve fetching metadata, but it raises other problems. For example, when a proxy is enabled, the server isnât found when I browse app.plex.tv â it does if I login via localhost 127.0.0.1:32400.
However, something else fails because of the repeated Target service not allowed errors. Iâm assuming my PMS canât be accessed from the outside when a proxy is enforced. Any ideas?
I am afraid there are always issues with the operation of Plex Media Server and the python agent and system bundle processes when there is a proxy. You can search the support articles and you will see that proxy crops up in many cases as something to check https://support.plex.tv/articles/?s=proxy&search=support_articles
Any news on this issue?
@gonse said:
Any news on this issue?
I donât have any info on this. It is between tmdb, cloudflare and ISP - there is no Plex involvement with how tmdb setup their data and the use of cloudflare is by them rather than plex
With regards to use of proxy, i mentioned that proxy software is known to cause probelms with operation of Plex Media Server. Heppy to look at logs but
We have made tmdb aware of the issue in Argentina - they will be contacting Cloudflare
The problem is being investigated by tmdb / cloudflare - they have asked for anyone with the issue to provide the output from this request
https://image.tmdb.org/cdn-cgi/trace
There is no harm in also providing traceroute image.tmdb.org output
If anyone still affected in Argentina please post the results here
The problem is being investigated by tmdb / cloudflare - they have asked for anyone with the issue to provide the output from this request https://image.tmdb.org/cdn-cgi/trace
maxi@server:~$ curl -L https://image.tmdb.org/cdn-cgi/trace
fl=44f42
h=image.tmdb.org
ip=190.247.xxx.xxx
ts=1525273181.197
visit_scheme=https
uag=curl/7.47.0
colo=EZE
spdy=off
http=http/1.1
loc=AR
There is no harm in also providing traceroute image.tmdb.org output
maxi@server:~$ traceroute image.tmdb.org
traceroute to image.tmdb.org (104.16.58.155), 30 hops max, 60 byte packets
1 10.0.0.1 (10.0.0.1) 1.251 ms 2.280 ms 2.768 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 149-161-89-200.fibertel.com.ar (200.89.161.149) 22.801 ms 133-161-89-200.fibertel.com.ar (200.89.161.133) 19.113 ms 145-161-89-200.fibertel.com.ar (200.89.161.145) 14.409 ms
7 150-165-89-200.fibertel.com.ar (200.89.165.150) 17.083 ms 10.834 ms 10.778 ms
8 * * *
9 104.16.58.155 (104.16.58.155) 12.265 ms 10.550 ms 9.678 ms
Let me know if you need anything else.
Thanks for the help.
Thanks for the feedback.
Will need to do some further tests and will be progressing this issue in this forum topic http://forums.plex.tv/discussion/316062/problem-downloading-artwork-from-tmdb-argentina-users/p1
See my last post here
http://forums.plex.tv/discussion/comment/1666171/#Comment_1666171
Would like to know if this issue is resolved?
Last info I have in this forum topic Problem downloading artwork from TMDB (Argentina Users) is that the ISP providing an alternative router fixed the problem
I think I qualify for the same issue: Ubuntu Server + plex & IPv6 disabled & Argentina & Fibertel & timeout on TMDB. Seems not solved. It may be because of the Technicolor DPC3848VE modem from Fibertel.
A number of users have reported the issue was resolved after Fibertel replaces the Technicolor modem/router with sagemcom
I can confirm this. My Technicolor was replaced by a Sagemcom modem and Plex is now back to its usual greatness. Metadata now loads in seconds
Lol, tried all kind of solutions. But this was the simplest one and it did the trick. Much love
I have the issue too, but I donât use the Technicolor cablemodem as router, mine is in bridge mode and I have a pfSense as firewall router. with the public IP address.
