For the longest time, to access Facebook, just changing my dns to use either google or opendns worked for me. However that trick doesn’t work anymore because all the IP Addresses that facebook.com normally resolves to have been blocked by the ISPs in Vietnam. I had resorted to using sshuttle – which creates a tunnel between my laptop and my server in the US. It worked, but it was slow. However yesterday one of my friends gave me a list of IP Addresses for Facebook which haven’t been blocked yet. These can be added to your
hosts file and you should be able to access Facebook again!
22.214.171.124 facebook.com 126.96.36.199 apps.facebook.com 188.8.131.52 login.facebook.com 184.108.40.206 graph.facebook.com 220.127.116.11 static.ak.connect.facebook.com 18.104.22.168 developers.facebook.com 22.214.171.124 error.facebook.com 126.96.36.199 fbcdn-profile-a.akamaihd.net 188.8.131.52 fbcdn-sphotos-a.akamaihd.net 184.108.40.206 fbcdn-photos-a.akamaihd.net 220.127.116.11 facebook.com 18.104.22.168 www.facebook.com 22.214.171.124 apps.facebook.com 126.96.36.199 facebook.com 188.8.131.52 www.facebook.com 184.108.40.206 apps.facebook.com 220.127.116.11 login.facebook.com 18.104.22.168 graph.facebook.com 22.214.171.124 static.ak.connect.facebook.com 126.96.36.199 developers.facebook.com 188.8.131.52 error.facebook.com 184.108.40.206 upload.facebook.com 220.127.116.11 register.facebook.com 18.104.22.168 bigzipfiles.facebook.com 22.214.171.124 pixel.facebook.com 126.96.36.199 apps.facebook.com 188.8.131.52 facebook.com 184.108.40.206 www.facebook.com 220.127.116.11 login.facebook.com 18.104.22.168 photos-a.ak.fbcdn.net 22.214.171.124 photos-b.ak.fbcdn.net 126.96.36.199 photos-c.ak.fbcdn.net 188.8.131.52 photos-d.ak.fbcdn.net 184.108.40.206 photos-e.ak.fbcdn.net 220.127.116.11 photos-f.ak.fbcdn.net 18.104.22.168 photos-g.ak.fbcdn.net 22.214.171.124 photos-h.ak.fbcdn.net
If you’re on Linux, add the above entries to
/etc/hosts. For Windows, I think the path is =>
c:\WINDOWS\system32\drivers\etc\hosts. This Wikipedia Article should help in case you need to figure out where your hosts file is.
Hope this helps.
Hey Pratik, it’s working again!
Thanks a lot for your effort!
right, opendns is no longer of help.
Came here looking for a solution, but yours isn’t working (for me).
Instead I use ultrasurf now. Works just fine.
I have tweaked the list, would be cool if you could check if it works for you or not.
I guess it’s only a matter of time before these are blocked too.
However I don’t understand why using this workaround would cause an invalid certificate warning. Is it an out and out invalid certificate warning or a certificate warning of some other type?
Could mean one of the following things:
(1) At least one of these IP address is not Facebook’s
(2) Browser is unable to check the certificate (but this would cause a lesser error)
(3) ISP is tampering with the actual certificate being served by Facebook.
And I would emphasise that in this day and age it is never safe to automatically ignore a certificate warning. It could be innocuous but I would not automatically ignore it for anything that mattered.
yes actually, did lil more googling, these IP Addresses point to a248.e.akamai.net. Facebook uses akamai for content delivery. So pointing to akamai works instead of pointing to facebook directly. And there’s a very good chance these IP Addresses won’t be blocked, because many companies use akamai for content delivery.
Lisa Warden liked this on Facebook.