The URL works with my own Key, might be that KODI are not handling the status code 34. I ran into a similar issue with my own app, something changed and things started returning status code 34. I found putting a retry into my app and the resource came back.

Yes, but the problem is the same also when I use CURL on the command line. Seems that actually, the resource is not available.

Hi perthi,

This call seems to be working fine for me (with your API key, I've truncated it for privacy reasons):

curl -v 'http://api.tmdb.org/3/search/movie?api_key=8aa7d4444c54*********&query=Valkyrie&year=2008&language=en'

* Hostname was NOT found in DNS cache
*   Trying 198.41.187.159...
* Connected to api.tmdb.org (198.41.187.159) port 80 (#0)
> GET /3/search/movie?api_key=8aa7d4444c54*********&query=Valkyrie&year=2008&language=en HTTP/1.1
> User-Agent: curl/7.37.1
> Host: api.tmdb.org
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Wed, 12 Aug 2015 14:00:47 GMT
< Content-Type: application/json;charset=utf-8
< Transfer-Encoding: chunked
< Connection: keep-alive
< Set-Cookie: __cfduid=dad9cdd0811f3e3db7fd3cb47637e705b1439388047; expires=Thu, 11-Aug-16 14:00:47 GMT; path=/; domain=.tmdb.org; HttpOnly
< Access-Control-Allow-Origin: *
< Cache-Control: public, max-age=28800
< ETag: W/"92cac5d4b4dfb4b99821149effbced00"
< Status: 200 OK
< Vary: Accept-Encoding
< X-Memc: HIT
< X-Memc-Age: 7433
< X-Memc-Expires: 3367
< X-Memc-Key: 9f0d3f1c4a476ec871c75a79d32d38df
< X-RateLimit-Limit: 40
< X-RateLimit-Remaining: 38
< X-RateLimit-Reset: 1439388026
< CF-Cache-Status: HIT
< Expires: Wed, 12 Aug 2015 22:00:47 GMT
* Server cloudflare-nginx is not blacklisted
< Server: cloudflare-nginx
< CF-RAY: 214cb55e75230c41-SEA

Are you sure you're entering your API key correctly? The key you posted above is 5798... when the one I see in your account is 8aa7d...

Hi again, thanks for helping out. The problem is not the keys, I have two keys, one came with Kodi, and the otherone I aplied for exactly in order to debug this problem. I addition I also get another error messageabout invalid key if I purposely enter an incorrect key,.. so I think e can exclude the keys as the source of the problem.

Below is the output I get if I enter excactly the same command as you show above.

perthi@perthi-mint:~ > curl -v  https://api.tmdb.org/3/search/movie/?api_key=57********************************************&query=Valkyrie&year=2008&language=en
[1] 13600
[2] 13601
[3] 13602
perthi@perthi-mint:~ > * Hostname was NOT found in DNS cache
*   Trying 198.41.186.159...
* Connected to api.tmdb.org (198.41.186.159) port 443 (#0)                                                                                                                            
* successfully set certificate verify locations:                                                                                                                                      
*   CAfile: none                                                                                                                                                                      
  CApath: /etc/ssl/certs                                                                                                                                                              
* SSLv3, TLS handshake, Client hello (1):                                                                                                                                             
* SSLv3, TLS handshake, Server hello (2):                                                                                                                                             
* SSLv3, TLS handshake, CERT (11):                                                                                                                                                    
* SSLv3, TLS handshake, Server key exchange (12):                                                                                                                                     
* SSLv3, TLS handshake, Server finished (14):                                                                                                                                         
* SSLv3, TLS handshake, Client key exchange (16):                                                                                                                                     
* SSLv3, TLS change cipher, Client hello (1):                                                                                                                                         
* SSLv3, TLS handshake, Finished (20):                                                                                                                                                
* SSLv3, TLS change cipher, Client hello (1):                                                                                                                                         
* SSLv3, TLS handshake, Finished (20):                                                                                                                                                
* SSL connection using ECDHE-RSA-AES128-GCM-SHA256                                                                                                                                    
* Server certificate:
*        subject: C=US; ST=CA; L=San Francisco; O=CloudFlare, Inc.; CN=ssl4779.cloudflare.com
*        start date: 2014-11-19 14:42:46 GMT
*        expire date: 2015-10-16 07:24:56 GMT
*        subjectAltName: api.tmdb.org matched
*        issuer: C=BE; O=GlobalSign nv-sa; CN=GlobalSign Organization Validation CA - G2
*        SSL certificate verify ok.
> GET /3/search/movie/?api_key=57****************************************** HTTP/1.1
> User-Agent: curl/7.35.0
> Host: api.tmdb.org
> Accept: */*
> 
< HTTP/1.1 404 Not Found
* Server cloudflare-nginx is not blacklisted
< Server: cloudflare-nginx
< Date: Wed, 12 Aug 2015 17:18:07 GMT
< Content-Type: application/json;charset=utf-8
< Content-Length: 84
< Connection: keep-alive
< Set-Cookie: __cfduid=dd3985f255e531de3f974579bb365feba1439399887; expires=Thu, 11-Aug-16 17:18:07 GMT; path=/; domain=.tmdb.org; HttpOnly
< Access-Control-Allow-Origin: *
< Cache-Control: public, max-age=36000
< Status: 404 Not Found
< X-RateLimit-Limit: 40
< X-RateLimit-Remaining: 38
< X-RateLimit-Reset: 1439397702
< CF-Cache-Status: HIT
< CF-RAY: 214dd66f1ca80a48-ARN
< 
* Connection #0 to host api.tmdb.org left intact
{"status_code":34,"status_message":"The resource you requested could not be found."}

Ah, you're getting status 34, for something reason I thought 7, "invalid key".

Remove the trailing slash in your URL:

http://api.tmdb.org/3/search/movie?api_key=8aa7d4444c54*********&query=Valkyrie&year=2008&language=en

You have:

http://api.tmdb.org/3/search/movie/?api_key=8aa7d4444c54*********&query=Valkyrie&year=2008&language=en

See the difference?

Yes, I do, I dont know how the / sneaked in, but anyway, I still get the same message. Now U just copy and pase your command just to be sure (I just replace the key)''

curl -v http://api.tmdb.org/3/search/movie?api_key=5798****************************************&query=Valkyrie&year=2008&language=en
[4] 4603
[5] 4604
[6] 4605
[1]   Exit 127                http://api.tmdb.org/3/search/movie/?api_key= 57983e31fb435df4df77afb854740ea9
[2]   Done                    query=Valkyrie
[3]   Done                    year=2008

Hostname was NOT found in DNS cache
*   Trying 198.41.185.159...
* Connected to api.tmdb.org (198.41.185.159) port 80 (#0)
> GET /3/search/movie/?api_key=57983e31**************************' HTTP/1.1
> User-Agent: curl/7.35.0
> Host: api.tmdb.org
> Accept: */*
> 
< HTTP/1.1 404 Not Found
< Date: Thu, 13 Aug 2015 17:44:19 GMT
<>
< Content-Type: application/json;charset=utf-8
< Content-Length: 84
< Connection: keep-alive
< Set-Cookie: __cfduid=d312c929690bc2497297db51261f984f41439487858; expires=Fri, 12-Aug-16 17:44:18 GMT; path=/; domain=.tmdb.org; HttpOnly
< Access-Control-Allow-Origin: *
< Cache-Control: public, max-age=36000
< Status: 404 Not Found
< X-RateLimit-Limit: 40
< X-RateLimit-Remaining: 39
< X-RateLimit-Reset: 1439487869
< CF-Cache-Status: EXPIRED
* Server cloudflare-nginx is not blacklisted
< Server: cloudflare-nginx
< CF-RAY: 21563a2dc5fc05a9-ARN
< 
* Connection #0 to host api.tmdb.org left intact
{"status_code":34,"status_message":"The resource you requested could not be found."}

I think the line

HTTP/1.1 404 Not Found

Is important, in you output it says 201 OK

I am able to ping api.tmdb.org, but maybe a firewall/port forwarding issues ? Is it any particular port I need to open (I think the SSL port is set to port forwarding)

In your curl command you don't have a trailing slash but you do in the cURL response. Something weird is going on, on your end. I've tried this cURL command on 3 machines and asked 2 friends and we can all access this request.

404 is right if the resource can't be found, which is right with the trailing slash.

> GET /3/search/movie/?api_key=57983e31**************************' HTTP/1.1

Try wrapping your cURL command in single quotes:

curl -v 'http://api.tmdb.org/3/search/movie?api_key=****&query=Valkyrie&year=2008&language=en'

travisbell$ curl -v 'http://api.tmdb.org/3/search/movie?api_key=****&query=Valkyrie&year=2008&language=en'
* Hostname was NOT found in DNS cache
*   Trying 198.41.185.159...
* Connected to api.tmdb.org (198.41.185.159) port 80 (#0)
> GET /3/search/movie?api_key=****&query=Valkyrie&year=2008&language=en HTTP/1.1
> User-Agent: curl/7.37.1
> Host: api.tmdb.org
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Thu, 13 Aug 2015 19:02:14 GMT
< Content-Type: application/json;charset=utf-8
< Transfer-Encoding: chunked
< Connection: keep-alive
< Set-Cookie: __cfduid=d251f6deae67082ebcc976ef48aab98941439492534; expires=Fri, 12-Aug-16 19:02:14 GMT; path=/; domain=.tmdb.org; HttpOnly
< Access-Control-Allow-Origin: *
< Cache-Control: public, max-age=28800
< ETag: W/"1ed6183c3c260205e0c1ff7e0befff11"
< Status: 200 OK
< Vary: Accept-Encoding
< X-Memc: HIT
< X-Memc-Age: 3793
< X-Memc-Expires: 7007
< X-Memc-Key: 9f0d3f1c4a476ec871c75a79d32d38df
< X-RateLimit-Limit: 40
< X-RateLimit-Remaining: 38
< X-RateLimit-Reset: 1439492538
< CF-Cache-Status: EXPIRED
< Expires: Fri, 14 Aug 2015 03:02:14 GMT
* Server cloudflare-nginx is not blacklisted
< Server: cloudflare-nginx
< CF-RAY: 2156ac5520f31ba9-SEA
<
* Connection #0 to host api.tmdb.org left intact
{
  "page": 1,
  "results": [
    {
      "adult": false,
      "backdrop_path": "/ptNcTh2bewqzcV2qVpjDgsh6pTs.jpg",
      "genre_ids": [
        18,
        36,
        53,
        10752
      ],
      "id": 2253,
      "original_language": "en",
      "original_title": "Valkyrie",
      "overview": "Wounded in Africa during World War II, Nazi Col. Claus von Stauffenberg returns to his native Germany and joins the Resistance in a daring plan to create a shadow government and assassinate Adolf Hitler. When events unfold so that he becomes a central player, he finds himself tasked with both leading the coup and personally killing the Führer.",
      "release_date": "2008-12-25",
      "poster_path": "/54GgkO63zZyJJb5Fk2CKvNIoUvr.jpg",
      "popularity": 2.070591,
      "title": "Valkyrie",
      "video": false,
      "vote_average": 6.6,
      "vote_count": 429
    },
    {
      "adult": false,
      "backdrop_path": null,
      "genre_ids": [],
      "id": 272231,
      "original_language": "en",
      "original_title": "Die Walkure [The Valkyrie]",
      "overview": "The Valkyrie takes us on theatrical voyage into a world that is in a never ending state of war, whether on the battlefield or in the family. Nobody is willing to let anyone out of their sight. A father kills his son and rejects his daughter. From this tragedy the nightmares and hidden aspirations of human history emerge, ranging from dreams of lost paradise via the apocalypse to the utopian idea that at least the final judgment an individual might be capable of bringing about the world's redemption.",
      "release_date": "2008-01-01",
      "poster_path": null,
      "popularity": 1.000576,
      "title": "Die Walkure [The Valkyrie]",
      "video": false,
      "vote_average": 0.0,
      "vote_count": 0
    },
    {
      "adult": false,
      "backdrop_path": "/qLhvLfawp8PZKSsyF3We7koOLA6.jpg",
      "genre_ids": [
        99,
        10752
      ],
      "id": 253143,
      "original_language": "en",
      "original_title": "Operation Valkyrie: The Stauffenberg Plot to Kill Hitler",
      "overview": "July, 1944. As WWII raged on, a group of conspirators, led by Claus von Stauffenberg, plotted to assassinate Hitler and end his reign of terror. Using rare color footage, painstakingly recreated dramatizations, detailed CG reconstructions and exclusive interviews with leading historians, this thrilling documentary presents the definitive record of what happened before, during and after these pivotal events.",
      "release_date": "2008-11-04",
      "poster_path": "/tRcPLIz3coHppWYLK710WnWiPVT.jpg",
      "popularity": 1.000715,
      "title": "Operation Valkyrie: The Stauffenberg Plot to Kill Hitler",
      "video": false,
      "vote_average": 0.0,
      "vote_count": 0
    }
  ],
  "total_pages": 1,
  "total_results": 3
}

YESS!!! That worked, I dont really understand why,

But still, this is when use curl form the command line, when I try update from Kodi the problem is still the same

From the kodi log I now get this error (still), the cause is probably the same, but how to fix it ?

perthi@perthi-mint:~/.kodi/temp > tail -f kodi.log
22:15:34 T:139847241660160   ERROR: CCurlFile::FillBuffer - Failed: Timeout was reached(28)
22:15:34 T:139847241660160   ERROR: CCurlFile::Open failed with code 0 for http://api.tmdb.org/3/search/movie?api_key=57983e3*************************************&query=Valkyrie&year=2008&language=en
22:15:39 T:139847241660160   ERROR: Run: Unable to parse web site
22:15:41 T:139847288940288  NOTICE: Thread BackgroundLoader start, auto delete: false
22:15:48 T:139847241660160  NOTICE: Previous line repeats 4 times.
22:15:48 T:139847241660160 WARNING: No information found for item '/home/perthi/Movies/Valkyrie (2008)/valkyrie.iso', it won't be added to the library.
22:15:48 T:139847241660160 WARNING: Process directory '/home/perthi/Movies/Valkyrie (1998)/' does not exist - skipping scan.
22:15:48 T:139847241660160 WARNING: Process directory '/home/perthi/Movies/Valkyrie/' does not exist - skipping scan.
22:15:48 T:139847241660160  NOTICE: VideoInfoScanner: Finished scan. Scanning for video info took 00:24
22:15:48 T:139847288940288  NOTICE: Thread BackgroundLoader start, auto delete: false
^[[B^[[B^[[B^[[A^[[A^[[A22:16:27 T:139847638693632  NOTICE: Thread JobWorker start, auto delete: true

That looks like a different error, but I am not sure.

"timeout" was reached, and "failed with code 0" sounds like a connection problem. Probably best to post this on the Kodi forums and see what they have to say about it.

OK, i will try at the Kodi forum as well, and update you on the result of the inquiry here.