The Flickr image does not exists or is private for all images

Both links you pasted are correctly imported on my local setup.

Can you check the following:
- Your flickr provider module is up to date.
- You entered a valid Flickr API key (admin/config/media/scald_flickr)

I am seeing this same behavior with the most current production and dev versions of scald and scald_flickr.

For my case, this goes back to a change currently being made in the flickr rest API. The flickr code blog states the change to all SSL begins June 27, 2014. However all new API keys issued after May 6, 2014 are SSL only:

Change in new API keys: 6 May 2014 (If you request a new API key after 6 May, it will be issued for HTTPS only)

Because of this change a standard request to a resource on flickr using non-SSL returns a failure.

Example:
http://api.flickr.com/services/rest/?method=flickr.photos.getInfo&api_ke...
{"stat":"fail", "code":95, "message":"SSL is required"}

While when you change the request to SSL it is successful:
https://api.flickr.com/services/rest/?method=flickr.photos.getInfo&api_k...
{"photo":{"id":"9238965898", "secret":"3a1fd996fb", "server":"3672", "farm":4, "dateuploaded":"1373275266", "isfavorite":0, "license":"3", "safety_level":"0", "rotation":0, "originalsecret":"4d9af1eeb4", "originalformat":"jpg", "owner":{"nsid":"79027397@N04", "username":"Museu Valenci\u00e0 d'Etnologia. Diputaci\u00f3 de Val\u00e8nc", "realname":"Museu Valenci\u00e0 d'Etnologia", "location":"Val\u00e8ncia, Espa\u00f1a", "iconserver":"7167", "iconfarm":8, "path_alias":"museuvalenciaetnologia"}, "title":{"_content":"Museu dHortadAlmassera_etnologia (23)"}, "description":{"_content":"Inauguiraci\u00f3n 5 de julio"}, "visibility":{"ispublic":1, "isfriend":0, "isfamily":0}, "dates":{"posted":"1373275266", "taken":"2013-07-05 20:35:58", "takengranularity":"0", "lastupdate":"1373275273"}, "views":"77", "editability":{"cancomment":0, "canaddmeta":0}, "publiceditability":{"cancomment":1, "canaddmeta":0}, "usage":{"candownload":1, "canblog":0, "canprint":0, "canshare":1}, "comments":{"_content":"0"}, "notes":{"note":[]}, "people":{"haspeople":0}, "tags":{"tag":[]}, "urls":{"url":[{"type":"photopage", "_content":"https:\/\/www.flickr.com\/photos\/museuvalenciaetnologia\/9238965898\/"}]}, "media":"photo"}, "stat":"ok"}

In the same blog post above they also state that all resources both API and website will shortly be SSL-only.

Question: Are all http://www.flickr.com urls going to be HTTPS from now on?
Answer: Yes, all http://www.flickr.com urls returned by the API are now HTTPS, and all requests to HTTP in the browser are redirected to HTTPS.

And they encourage app developers to switch all links to SSL:

If you already call the API over HTTPS, then you’re good. No action needed. But if your code currently calls the API over HTTP, then, YES, you do need to do something. In your code you need to change the protocol to HTTPS. Like this: https://api.flickr.com/

Attached is a patch which converts these calls to HTTPS to match what is recommended. Because there is a redirect already in place to handle bit.ly and other shorteners, it also captures non-SSL flickr links and they resolve to https with this patch. As a separate patch we may want to consider allowing SSL-redirects in the future.

Thx stupiddingo, i will check this patch as soon as possible.

pushed !