"Error whitelisting" when trying to whitelist a domain from 'Stats' blocked list

Follow
Avatar
acatic1

I cannot seem to unblock any domain when working from the blocked domains list.  When I click to whitelist a corresponding blocked domain, I get a popup saying "error whitelisting", with no details.  I can manually enter the domain with the 'never block' function still.  However, it would be very handy to unblock straight from the blocked domains list, especially since the link is provided, but does not appear to work.

Thanks for any guidance!

1

Comments

29 comments

Sort by Date Votes
  • Official comment
    Avatar
    Anthony Attwood

    Thanks for raising this issue. Our engineers are aware of the problem and are looking into a resolution. As has been pointed out, in the meantime you can still add domains to the block and allow lists manually, it is just the quick add from reports that is not functioning.

    Comment actions Permalink
  • Avatar
    mattwilson9090

    I just checked and am getting the same thing. You should open a support ticket since something on the website seems to be broken.

    0
    Comment actions Permalink
  • Avatar
    mel_davila

    From Rank Domain I have the same problem.

    Cliking in 

    make an exception for this domain.

      *.youtube.com 1,484
     
    This domain is categorized as Video Sharing, which you blocked.

               Error whitelisting *.youtube.com

     

    0
    Comment actions Permalink
  • Avatar
    rotblitz (Edited )

    No, mel_davila, you have an absolutely different problem.  You generally cannot whitelist or blacklist a wildcard (this is an expression with an "*").  If you whitelist or blacklist without the *, i.e. youtube.com in your case, it should work.

    -1
    Comment actions Permalink
  • Avatar
    mel_davila

    To reproduce the error:
    go to Stats.
    Click on "blocked domain"
    remove all filters and apply.
    Select (click) one in red (blocked).
    With "*" or without and try to "make an exception for this domain"
    I have always the same error.
       Error whitelisting ........

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    And what exactly is this "always the same error"?  You didn't say what the error message is...  
    I have tried this too, and if I get an error message, it is very explicit although not always helpful.

    -1
    Comment actions Permalink
  • Avatar
    atombomb6666

    I have the same error every time too even using different browsers.See image below...

     

     

     

    3
    Comment actions Permalink
  • Avatar
    rotblitz (Edited )

    I'm confident that you raised a support ticket.  If not, I'll raise one.

    Edit:  Ok, I have opened a ticket: 250922

    -1
    Comment actions Permalink
  • Avatar
    zirafa

    It still seems like it would not be working.

     

    1
    Comment actions Permalink
  • Avatar
    rotblitz

    Yes, this has apparently less priority, because it does not prevent from blacklisting or whitelisting domains.  This can still easily be done from https://dashboard.opendns.com/settings/ with no errors.

    -4
    Comment actions Permalink
  • Avatar
    zirafa

    Ah, I see. So after half a bloody year we cannot fix a simple issue. Right. Seems legit. I wish I could afford to work in such a hurry :)

    0
    Comment actions Permalink
  • Avatar
    rotblitz (Edited )

    Honestly, I'm user since 2007 and I do not recall that I really needed that feature.  In most cases it does not make sense to block what is being offered in the domain stats, because you want to either block more (e.g. example.com instead of blog.example.com) or less (e.g. my.subdomain.example.org instead of example.org).

    Also, think about, it's a free service, even not ad driven like so many others.  What do you expect then...

    -5
    Comment actions Permalink
  • Avatar
    the.tates

    I'm  a new user having this issue as well.  Looks like its been going on a while and still not fixed.  What's up Cisco?

    3
    Comment actions Permalink
  • Avatar
    rotblitz (Edited )

    Beside you and me, only four users (out of 65 millions) complained about this malfunctioning feature.  Do you really think this convinces Cisco/OpenDNS to work on this?  (If I was them, I didn't work on it either...)

    In the meantime you may want wasting your time with calculating the percentage of complaining users... ;-)

    -6
    Comment actions Permalink
  • Avatar
    zirafa

    Rotblitz, how about putting the effort you put into offending the affected users to solving this problem? What the hack should this approach actually mean? I do not need this, therefore you are a bunch of idiots and we don't need to solve the bug? Really? Go to hell with such responses and better find a solution or shut up since you cannot be helpful.

    1
    Comment actions Permalink
  • Avatar
    rotblitz

    "how about putting the effort ... to solving this problem?"

    Sure, I'll fix it immediately after you provided me access to the source code.  No problem!  Awaiting you granting me access...

    Wondering about something?  Well, if I can fix the problem, you can grant access to the code, not?  Why not?

    -5
    Comment actions Permalink
  • Avatar
    seawolfves

    Some one doing something about this has been going on for months

    3
    Comment actions Permalink
  • Avatar
    cindybnp

    Ridiculous.This has been a problem now for years with no resolution. Very poor service. OpenDNS you get ZERO stars,

    2
    Comment actions Permalink
  • Avatar
    rotblitz

    What amount did you pay for the service?

    -4
    Comment actions Permalink
  • Avatar
    cindybnp

    rotblitz, why are you spamming this thread?

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    I see, you spammer paid nothing for the service but want as much as possible.

    -4
    Comment actions Permalink
  • Avatar
    cindybnp

    You are the punk spammer. Harassing everyone who asks for help or comments on the service. Bark up another tree. None of your business loser.

    0
    Comment actions Permalink
  • Avatar
    storic

    Sorry to bring this up again, but I'm having the same error.

    Has this not been fixed for the last 3 years?

    2
    Comment actions Permalink
  • Avatar
    takver

    Same error. 4 years since posted. Is anyone looking at those posts? 

    0
    Comment actions Permalink
  • Avatar
    brian

    Hi

    I'm having the same issue, however found a work around. In the settings tab, when using custom filtering, at the bottom of the page is a dropdown. You can always block, or never block domains you add here. Select never block, and add the domain that's getting blocked. You can find the domain that's getting blocked on the stats tab (be sure you have stats enabled).

    0
    Comment actions Permalink
  • Avatar
    bleurgh

    Yep, I'm still having this problem as of Jan. 2021.  Apparently it's not a priority, although you can still add the domains manually. 

    0
    Comment actions Permalink
  • Avatar
    zaxy

    Rotten Blitz needs to realize that free and open source is not a curtain to hide buggy products behind. If the openDNS team has even a little bit of pride they would fix this ASAP. The workaround is crap.

    0
    Comment actions Permalink
  • Avatar
    www.proxycap.com

    Paying for the service and am unable to do this very thing - sad that this is still an open issue after this many years...

    0
    Comment actions Permalink
  • Avatar
    vkumar123456789

    This is an ancient bug, that still haunts in 2022

    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post