Ping to www.facebook.com is ok but cannot access from chrome
-
Hello there.
Recently about a week ago. I had this strange thing happened to my chrome not being able to go to facebook page. I typed www.facebook.com on chrome address bar and press enter as I would normally did it did not load the facebook page but instead it said "This site can’t be reached". I thought the failed to resolve but when i ping www.facebook.com I received replies. Also I noticed before when i just typed www.facebook.com without https it would just to change to a secure site with a padlock icon added. Now no more padlock was added but instead I received the page below
When I clicked on information icon, it said is not secured, see below
These the things I've done.
- changeed browser to Microsoft Edge, then Firefox and the problem still persisted
- Did a Reset and Clean
- Disabled pfblockeerNG and re-enabled it again and restarted my laptop
- ipconfig /flushds
- changed my dns from 8.8.8.8 to 1.1.1.1 on my laptop
none of the above worked.
Any suggestion. I realized that it did not just happened to me only , users on my network are now experiencing the same issue.
-
@john-tiota said in Ping to www.facebook.com is ok but cannot access from chrome:
when i ping www.facebook.com I received replies
Even before the lines with the 'ping' reply start to repeat, some important information is shown.
What was it ?@john-tiota said in Ping to www.facebook.com is ok but cannot access from chrome:
Disabled pfblockeerNG and re-enabled it again and restarted my laptop
I would change that test.
Disabled pfblockeerNG.
Just for conscious, reboot pfSense, reboot PC.
Now do all the testing.The result of this method will bring to the next phase :
a) It was pfBlockerNG : "say to yourself : next time, before I include a feed (DNSBL) into pfBlockerNG, I read it first" (as there is no sense in using pfBlockerNG with feeds that lists sites that you actually visit ;) ) Or check the the pfB alert list, and white list sites that were blocked.
b) Call facebook **, your ISP, or who ever manages your uplink connection.** as we now know for sure, they can also mess up things.
-
Same happened to me. When I ping www.facebook.com I also received this.
With regard to what Gertjan said the only information I noticed was that the first line in the reply showed
star-mini.c10r.facebook.com.
Then I disabled pfblockedNG,reboot pfsense and my laptop. Then things seemly solved, my facebook was now back online, well at lease for now.
My question is what really happened that made this. It was very frustrating for me since this is very strange. -
@wintok said in Ping to www.facebook.com is ok but cannot access from chrome:
My question is what really happened that made this. It was very frustrating for me since this is very strange
Read this, which is great humour btw.
I tested mysef :
I visited facebook.com with a browser.
I located facebook.com in the pfBlockerNG-devel Unified log..
I added the domain "facebook.com" as a wildcard blokced domain name, by clicking on + etc etc etc..
Now, it shows in red (blocked). See the image :
I flushed my local (on PC) DNS cache, and visited facebook again.
There was an issue :
I could also do what the guy in the reddit post was asking : include a DNSBL feed with facebook.com listed.
( we all know why he did this, of course .... )Again : check your DNSBL (and IP !!) lists/feeds before you use them in pfBlockerNG-devel.
The browser (Edge) indicated that there was a DNS probing issue.
Sorry, my browser want to use the French language.Yeah, right, that would be ok, as facebook.com returns
0.0.0.0
( you can check for yourself with nslookup )
and 0.0.0.0 is not usable as a 'destination' IP address..
But I asked pfBlockerNG-devel to do exactly that !!
Adding a domain manually, like I did, or adding it by using a DNSBL feed, its all the same.