Facebook Images not displaying (possible opendns problem?)

Though I mostly use Chrome, Firefox is also affected.
Fresh Install of OpenSuse this morning; fresh download and install of Chrome.
OpenSUSE 12.3 (Dartmouth) (x86_64) KDE 4.10.00 “release 1”

Background: We’re using blockless.com for DNS in order to access US Netflix instead of lousy Canadian version.
This happens on my Linux machine, but not on a Windows XP machine on the same network.

As of the last few days, most images on Facebook do not appear. Trying to open the image in a tab generates the following:
UPDATE: Should note that it’s mostly Profile pictures and personal images that are blocked. Ads come through just fine. :slight_smile:

Link: https://fbcdn-profile-a.akamaihd.net/hprofile-ak-ash3/c72.37.466.466/s160x160/72401_10150295857835646_7585861_n.jpg

This is probably not the site you are looking for!
You attempted to reach fbcdn-profile-a.akamaihd.net, but instead you actually reached a server identifying itself as *.opendns.com. This may be caused by a misconfiguration on the server or by something more serious. An attacker on your network could be trying to get you to visit a fake (and potentially harmful) version of fbcdn-profile-a.akamaihd.net.
You should not proceed, especially if you have never seen this warning before for this site.
Proceed anyway Back to safety
https://forums.opensuse.org/image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAsAAAALCAYAAACprHcmAAAAMUlEQVQY02P4/8/A7GYgXaKgeA/0Riqg6BCFGcQUojhZnwKsXoQl0KcoYFNIW3DGQCkVyHtwOU6YQAAAABJRU5ErkJggg==Help me understand
When you connect to a secure website, the server hosting that site presents your browser with something called a “certificate” to verify its identity. This certificate contains identity information, such as the address of the website, which is verified by a third party that your computer trusts. By checking that the address in the certificate matches the address of the website, it is possible to verify that you are securely communicating with the website you intended, and not a third party (such as an attacker on your network).
In this case, the address listed in the certificate does not match the address of the website your browser tried to go to. One possible reason for this is that your communications are being intercepted by an attacker who is presenting a certificate for a different website, which would cause a mismatch. Another possible reason is that the server is set up to return the same certificate for multiple websites, including the one you are attempting to visit, even though that certificate is not valid for all of those websites. Google Chrome can say for sure that you reached *.opendns.com, but cannot verify that that is the same site as fbcdn-profile-a.akamaihd.netwhich you intended to reach. If you proceed, Chrome will not check for any further name mismatches.

For some reason in Firefox, no error message, the images just don’t appear.
Note: The OpenSUSE install was coincidental, replacing a Mint install. This problem appeared before that change

Google Chrome 26.0.1410.63 (Official Build 192696)
OS Linux
WebKit 537.31 (@147513)
JavaScript V8 3.16.14.11
Flash 11.7.700.169
User Agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.63 Safari/537.31
Command Line /opt/google/chrome/google-chrome --flag-switches-begin --flag-switches-end
Executable Path /opt/google/chrome/google-chrome
Profile Path /home/barry/.config/google-chrome/Default
Variations 95c1ed7-3d47f4f4

b03ddc1f-2d9ef0cc
f9b252d0-fd526c81
ca6785ad-766fa2d
3709139-766fa2d
ff3fc1a6-766fa2d
d86b76a4-766fa2d
7f6da4bf-37924bda
75f7fb7e-766fa2d
24dca50e-837c4893
ca65a9fe-91ac3782
3028188e-626278e
5e29d81-cf4f6ead
246fb659-7158671e
f296190c-17e37270
4442aae2-a90023b1
75f0f0a0-e1cc0f14
e2b18481-5c63917a
e7e71889-e1cc0f14|

On 2013-05-18 21:06, appalbarry wrote:

> Google Chrome can say for sure that you
> reached *.opendns.com, but cannot verify that that is the same site as
> fbcdn-profile-a.akamaihd.netwhich you intended to reach. If you proceed,
> Chrome will not check for any further name mismatches.

It looks to me as if you are using opendns.com as proxy.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

Yeah, that I know. the question is how to fix the problem; and why it doesn’t affect the Windows box using the same DNS.

can you try disabling ipv6 in yast and firefox and check whether issue still exists?

On 2013-05-19 06:56, appalbarry wrote:
>
> Yeah, that I know. the question is how to fix the problem; and why it
> doesn’t affect the Windows box using the same DNS.

I don’t even have a facebook profile, so I can not test. And I don’t use
any “funny” DNS setup like “blockless.com”, which from the very little I
have read acts like a proxy (I googled: there is no wikipedia article or
similar independent description).

Maybe it just does not support Linux or has instructions that you have
to follow - ask them. I did a search:


http://help.blockless.com/customer/portal/articles/search?q=linux

and got:

+++····················
0 results found for “linux”
····················+±


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

On 05/18/2013 09:06 PM, appalbarry wrote:
> As of the last few days, most images on Facebook do not appear.

as a point of reference, all photos/images/etc on facebook show
exactly as they normally have for years–with no problem encountered
from “the last few days” and into today with firefox, chrome,
chromium or opera…

try using Google’s free dns, and see if your problem goes away…


dd
http://tinyurl.com/DD-Software

Well, I haven’t had time to explore further, but it appears that Facebook images are returning. Slowly. A handful at a time.

I’m prepared to write it off as one of those odd Internet things. Or more likely one of those odd Facebook things.

Blockless.com is one of several companies that allow use of their custom DNS set ups to get around geographic blocks on content.

For instance if you’re in Canada and would prefer to watch the US version of Netflix (which has four times as much content as the Canadian version for the same price) you set your DNS to those supplied by blockless.com, and Netflix believes you’re in the US.

Because we access Netflix via a Sony Blu-ray player, which does not allow you to set separate DNS addresses for that unit, we instead have set up the household router to use this DNS.

It’s still a mystery why my Facebook lost images, but others in the same house didn’t.

On 2013-05-19 19:36, appalbarry wrote:
> ‘Blockless.com’ (https://www.blockless.com/) is one of several
> companies that allow use of their custom DNS set ups to get around
> geographic blocks on content.
>
> For instance if you’re in Canada and would prefer to watch the US
> version of Netflix (which has four times as much content as the Canadian
> version for the same price) you set your DNS to those supplied by
> blockless.com, and Netflix believes you’re in the US.

It is not as simple as changing the DNS, it has to do much more or it
will not work. It has to do some type of proxy or vpn service.

I have been unable to find on a quick google search how does it really work.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)