Block page doesn't work in all browsers

Follow

hankrearden22

February 25, 2019 19:50

Hi folks, I found similar posts, but not this specific issue - apologies if this has been asked/answered already:

Scenario: I wanted to block "instagram.com" at it's a major distraction for the kids doing homework (they don't have phones, but they do have access to the internet via the 2 laptops I make available for homework).

I've installed and configured OpenDNS - seems to be working great in general (I used the FamilyFriendly DNS servers on my router so porn is automatically filtered out before I have to lift a finger).

I then set up a free account, installed the IP updater on our home PC, enabled the OpenDNS setting to allow it to update (as we have a dynamic IP address).

Finally, I went to OpenDNS > Dashboard > Settings > Web Content Filtering and selected "Moderate" filtering level and added "instagram.com" as an "Always Blocked" domain.  I also set up a custom block page message with a picture of me and a message that says, "Do your homework, chumps."

Here's the problem: the site is successfully blocked, but the OpenDNS block page doesn't always come up.  Attached are 3 screenshots: trying to go to instagram.com from Internet Explorer, Firefox and Chrome.  Notice that Internet Explorer is the only one that makes it to the block page.

Admittedly, this is a minor issue: the main purpose has been accomplished - instagram is successfully blocked.  But why aren't they seeing the block pages in Chrome or Firefox (they mostly use Chrome as one of our machines is a chromebook)?

Thank you!

 

0

• 

  hankrearden22 February 25, 2019 19:58

  Also, I should point out, if on that Chrome screen you click "Proceed to www.instagram.com (unsafe)" - it just loops back to that same screen.  Similarly, in the firefox window, clicking the Add Exception does not allow the user to actually bypass the blocking.  OpenDNS' blocking is working - I just can't get it to display the proper block screen.

  0

  Comment actions Permalink
• 

  rotblitz February 27, 2019 13:04

  You missed an important article in the knowledge base:
  https://support.opendns.com/hc/en-us/articles/227988787
  This should solve your problem.

  1

  Comment actions Permalink
• 

  marlinputnam8745 March 14, 2019 06:36

  it is not possible to get Instagram blocked in chrome and firefox, it will redirect to add an exception or proceed to it, but if you had blocked it, the site will not open.

  0

  Comment actions Permalink
• 

  hankrearden22 March 14, 2019 18:43

  Thanks guys - rotblitz was right.  Once I added that certificate to the browsers in question, the proper blocked page began displaying correctly.

  0

  Comment actions Permalink
• 

  ketond January 05, 2023 01:50

  Why do all the support links lead to :

  oops

  The page you were looking for doesn't exist

  You may have mistyped the address or the page may have moved

  Take me back to the home page

  ?

   

  Makes it impossible to find answers

  0

  Comment actions Permalink
• 

  hankrearden22 January 05, 2023 12:46

  Hey ketond - I'm not sure why the links have changed, but if you're referring to the link that rotblitz originally provided in this thread, I think it's been updated to this:
  
  https://support.opendns.com/hc/en-us/articles/227987007-Block-Page-Errors-Installing-the-Cisco-Umbrella-Root-CA
  
  It's been a few years, but as I recall, after installing those certificates on the browsers in question the proper block page began showing up for my "users" (kids).

  0

  Comment actions Permalink

Please sign in to leave a comment.