But I said I can download it directly with a python script and also it loaded if I turn on my VPN

Inspect the response headers and you'll see that it's not the same. On the one that is working, you're being redirected (notice the HTTP/2 301):

curl -v "https://media.themoviedb.org/t/p/w220_and_h330_face/kCGlIMHnOm8JPXq3rXM6c5wMxcT.jpg"

*   Trying 37.19.207.34:443...
* Connected to media.themoviedb.org (37.19.207.34) port 443
* ALPN: curl offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/cert.pem
*  CApath: none
* (304) (IN), TLS handshake, Server hello (2):
* (304) (IN), TLS handshake, Unknown (8):
* (304) (IN), TLS handshake, Certificate (11):
* (304) (IN), TLS handshake, CERT verify (15):
* (304) (IN), TLS handshake, Finished (20):
* (304) (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / AEAD-AES256-GCM-SHA384
* ALPN: server accepted h2
* Server certificate:
*  subject: CN=media.themoviedb.org
*  start date: Mar 16 00:09:28 2024 GMT
*  expire date: Jun 14 00:09:27 2024 GMT
*  subjectAltName: host "media.themoviedb.org" matched cert's "media.themoviedb.org"
*  issuer: C=US; O=Let's Encrypt; CN=R3
*  SSL certificate verify ok.
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://media.themoviedb.org/t/p/w220_and_h330_face/kCGlIMHnOm8JPXq3rXM6c5wMxcT.jpg
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: media.themoviedb.org]
* [HTTP/2] [1] [:path: /t/p/w220_and_h330_face/kCGlIMHnOm8JPXq3rXM6c5wMxcT.jpg]
* [HTTP/2] [1] [user-agent: curl/8.4.0]
* [HTTP/2] [1] [accept: */*]
> GET /t/p/w220_and_h330_face/kCGlIMHnOm8JPXq3rXM6c5wMxcT.jpg HTTP/2
> Host: media.themoviedb.org
> User-Agent: curl/8.4.0
> Accept: */*
>
< HTTP/2 301
< date: Wed, 20 Mar 2024 18:11:22 GMT
< content-type: text/html
< content-length: 162
< location: https://image.tmdb.org/t/p/w220_and_h330_face/kCGlIMHnOm8JPXq3rXM6c5wMxcT.jpg
< server: BunnyCDN-ASB1-925
< cdn-pullzone: 1885712
< cdn-uid: 29af4e0e-bcbd-4fcb-8635-74ddc38a1ebf
< cdn-requestcountrycode: CA
< access-control-allow-origin: *
< access-control-allow-headers: Server, x-goog-meta-frames, Content-Length, Content-Type, Range, X-Requested-With, If-Modified-Since, If-None-Match
< access-control-expose-headers: Server, x-goog-meta-frames, Content-Length, Content-Type, Range, X-Requested-With, If-Modified-Since, If-None-Match
< cache-control: no-cache
< cdn-requestid: 2f945b2e2ef2f08d70f7877da96fc0b0
<

* Connection #0 to host media.themoviedb.org left intact

If you do the same on the network that isn't working, you'll see a different response.

Ok now I get it, thanks for the info It would be great if tmdb developer let us access images from media.themoviedb.org because image.tmdb.org is blocked here :(

Ok, great, happy to help.

With regards to your question unfortunately, that is not possible. They are different domains and networks on purpose and by design.

@mrj97 said:

Ok now I get it, thanks for the info It would be great if tmdb developer let us access images from media.themoviedb.org because image.tmdb.org is blocked here :(

+1, and thanks @mrj97 for perusing this topic further. Im returning to this question again, as the stop-gap solution is not permanent workable solution for me as well.

@travisbell
Will appreciate any alternative solution to this problem, using public DNS is not a viable option as it results is blocking of many diffrent sites, which were mitigated running AdGuard/self-hosted DNS/DPI network solutions. What are the chances what we can deploy any cacheing services such as cloudfront or any CDN like cloudflare -- these will be impossible for anyone to block.

I have sent an email to my ISP Airtel, but they are least bothered replying.

I use Cloudflare DNS (1.1.1.1) and GoodbyeDPI on PC to unblock TMDB and other sites banned by Indian government. On android I use Rethink which is basically GoodbyeDPI but for android.