Hello everyone!! Again the problem with requests :(

****-****-MacBook-Pro:Movies ****$ curl -v https://api.themoviedb.org/3/movie/587807?api_key=c5bc******************2a4b
*   Trying 13.33.240.18...
* TCP_NODELAY set
* Connection failed
* connect to 13.33.240.18 port 443 failed: Connection refused
*   Trying 13.33.240.4...
* TCP_NODELAY set
* Connection failed
* connect to 13.33.240.4 port 443 failed: Connection refused
*   Trying 13.33.240.129...
* TCP_NODELAY set
* Connection failed
* connect to 13.33.240.129 port 443 failed: Connection refused
*   Trying 13.33.240.55...
* TCP_NODELAY set
* Connection failed
* connect to 13.33.240.55 port 443 failed: Connection refused
* Failed to connect to api.themoviedb.org port 443: Connection refused
* Closing connection 0
curl: (7) Failed to connect to api.themoviedb.org port 443: Connection refused
***-***-MacBook-Pro:Movies ***$ 

Could not connect to the server.

****-****-MacBook-Pro:Movies ****$ curl -v https://api.themoviedb.org/3/movie/550?api_key=c5bc******************2a4b
*   Trying 13.227.219.97...
* TCP_NODELAY set
* Connected to api.themoviedb.org (13.227.219.97) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=*.themoviedb.org
*  start date: Nov 20 00:00:00 2020 GMT
*  expire date: Dec 19 23:59:59 2021 GMT
*  subjectAltName: host "api.themoviedb.org" matched cert's "*.themoviedb.org"
*  issuer: C=US; O=Amazon; OU=Server CA 1B; CN=Amazon
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x7fdddd00ba00)
> GET /3/movie/550?api_key=c5bc******************2a4b HTTP/2
> Host: api.themoviedb.org
> User-Agent: curl/7.64.1
> Accept: */*
> 
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 200 
< content-type: application/json;charset=utf-8
< content-length: 1778
< date: Fri, 05 Mar 2021 14:21:57 GMT
< server: openresty
< access-control-allow-origin: *
< access-control-allow-methods: GET, HEAD, POST, PUT, DELETE, OPTIONS
< access-control-expose-headers: ETag, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, Retry-After, Content-Length, Content-Range
< cache-control: public, max-age=21600
< x-memc: HIT
< x-memc-key: ade4da0c2a4d430121774a5494398f64a3949dda
< x-memc-age: 19302
< x-memc-expires: 2298
< etag: W/"4798f5c7383ad3a249564ddc1ce6253b"
< vary: Accept-Encoding,Accept-Encoding,Accept-Encoding
< x-cache: Miss from cloudfront
< via: 1.1 f5e34f7c59830a3caffb7df5f36b4daf.cloudfront.net (CloudFront)
< x-amz-cf-pop: AMS54-C1
< x-amz-cf-id: ClgndePxX1xoe-GabnxfzNeNWexLsnQBt7WRE2SvuvsALZ4sRc3gdQ==
< 
* Connection #0 to host api.themoviedb.org left intact
{"adult":false,"backdrop_path":"/52AfXWuXCHn3UjD17rBruA9f5qb.jpg","belongs_to_collection":null,"budget":63000000,"genres":[{"id":18,"name":"Drama"}],"homepage":"http://www.foxmovies.com/movies/fight-club","id":550,"imdb_id":"tt0137523","original_language":"en","original_title":"Fight Club","overview":"A ticking-time-bomb insomniac and a slippery soap salesman channel primal male aggression into a shocking new form of therapy. Their concept catches on, with underground \"fight clubs\" forming in every town, until an eccentric gets in the way and ignites an out-of-control spiral toward oblivion.","popularity":41.633,"poster_path":"/8kNruSfhk5IoE4eZOc4UpvDn6tq.jpg","production_companies":[{"id":508,"logo_path":"/7PzJdsLGlR7oW4J0J5Xcd0pHGRg.png","name":"Regency Enterprises","origin_country":"US"},{"id":711,"logo_path":"/tEiIH5QesdheJmDAqQwvtN60727.png","name":"Fox 2000 Pictures","origin_country":"US"},{"id":20555,"logo_path":"/hD8yEGUBlHOcfHYbujp71vD8gZp.png","name":"Taurus Film","origin_country":"DE"},{"id":54051,"logo_path":null,"name":"Atman Entertainment","origin_country":""},{"id":54052,"logo_path":null,"name":"Knickerbocker Films","origin_country":"US"},{"id":25,"logo_path":"/qZCc1lty5FzX30aOCVRBLzaVmcp.png","name":"20th Century Fox","origin_country":"US"},{"id":4700,"logo_path":"/A32wmjrs9Psf4zw0uaixF0GXfxq.png","name":"The Linson Company","origin_country":"US"}],"production_countries":[{"iso_3166_1":"DE","name":"Germany"},{"iso_3166_1":"US","name":"United States of America"}],"release_date":"1999-10-15","revenue":100853753,"runtime":139,"spoken_languages":[{"english_name":"English","iso_639_1":"en","name":"English"}],"status":"Released","tagline":"Mischief. Mayhem. Soap.","title":"Fight Club","video":false,"vote_average":8.4,"vote_count":21230}* Closing connection 0
****-****-MacBook-Pro:Movies ****$

It worked :)

Hi, everyone. It works.

Hello everyone! How did it work for you?

It didn’t work for me before and it doesn’t work now (without VPN or Cloudflare DNS). Did you do something for this?

Saint-Petersburg, Peterhof

I didn't do anything, I don't have a VPN enabled.

Since 25.02.2021 stopped working, requests began to pass successfully since 02.03.2021, today I noticed a failure - I wrote about it above - now requests began to pass successfully again

I use simple GET request for my iOS app. I didn't change anything after blocked. it worked today. Maybe RKN unlocked IP TMDB, but your internet provider is still block these IP or TMDB has made some changes in the API.

Hello everyone! I still get timeout or connection refused errors. Maybe someone has an update?

curl -v https://api.themoviedb.org/3/movie/550\?api_key\=<api_key>. 
*   Trying 13.33.240.129...  
* TCP_NODELAY set. 
* Connection failed  
* connect to 13.33.240.129 port 443 failed: Operation timed out  
*   Trying 13.33.240.55...  
* TCP_NODELAY set  
* Connection failed  
* connect to 13.33.240.55 port 443 failed: Operation timed out  
*   Trying 13.33.240.4...  
* TCP_NODELAY set  
* After 74083ms connect time, move on!  
* connect to 13.33.240.4 port 443 failed: Operation timed out  
*   Trying 13.33.240.18...  
* TCP_NODELAY set  
* After 37041ms connect time, move on!  
* connect to 13.33.240.18 port 443 failed: Operation timed out  
* Failed to connect to api.themoviedb.org port 443: Operation timed out  
* Closing connection 0  
curl: (7) Failed to connect to api.themoviedb.org port 443: Operation timed out  

I checked the link for possible blocking in Russia (https://isitblockedinrussia.com/?host=https%3A%2F%2Fapi.themoviedb.org). The IP addresses that we are trying to connect to are blocked.

I found one option to send requests bypass the blocking - it's simple... But I can't put it in the public here because the RKN will block it too.

@sunriser said:

I found one option to send requests bypass the blocking - it's simple... But I can't put it in the public here because the RKN will block it too.

You are a bad person. We all have a problem to solve, too, and a hint would be nice)

@idmotar said:

@sunriser said:

I found one option to send requests bypass the blocking - it's simple... But I can't put it in the public here because the RKN will block it too.

You are a bad person. We all have a problem to solve, too, and a hint would be nice)

I'm not "bad person" - I spoke about public... Send me your e-mail - I'll explaine how do.

@sunriser said:

I found one option to send requests bypass the blocking - it's simple... But I can't put it in the public here because the RKN will block it too.

Then, what is the point in your statements if you have not clarified anything? These are just words about nothing.

Megafon not pass request, with my changing - pass exelent.

These are still words about nothing. Nothing changed. What is your SOLUTION exactly?

What is the point of writing here for the third time that you solved the problem and not explaining its solution?

How does your logic work in the fact that you do not want publicity and at the same time offer to send a detailed explanation by email? Why won't RKN be able to block your "solution" in this case?