NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

LorneAv's avatar
LorneAv
Tutor
Oct 23, 2015
Solved

cannot sign in to openDNS account to set-up parental controls using NETGEAR Genie

Hi, I am trying to use NETGEAR Genie Parental controls and when I attempt to login to my OpenDNS account, I get the following error message: "There was an error signing, in please make sure you're ...
Genie
  • DexterJB's avatar
    DexterJB
    Oct 23, 2015

    Hi LorneAv,

     

    This has already been reported and is currently being looked at. I will be sending an inquiry to Engineering and will provide an update on this thread.

     

    Regards,

     

    Dexter

    Community Team

snowedin's avatar
snowedin
Initiate
Oct 24, 2015
I have the same issue with Genie login to setup Parental Controls.  I have a R7000 Netgear router with firmware version V1.0.4.30_1.1.67.   The Genie app for Windows v2.4.16 (I have Windows 10 x64 home premium) would not create a new OpenDNS account - did not like my password even though it met the criteria of 6-20 characters (the one I used had 10 chars, containing UPPER, lower, number and one special - the exclamation !.  Then I tried one that was 17 chars - Genie still didn't like it).  I went to OpenDNS.com and created a new OpenDNS account using my email address and the password I used in this case was 10 chars with Upper, lower, number and special; OpenDNS created an account.
 
Now using Genie with the existing OpenDNS account and password that I know works with the OpenDNS account.  Genie app tells me "There was an error signing in, make sure you are connected to the Internet and try again."  I am connected to the Internet as that is how I downloaded the Genie app...and how I am replying to this post...  I went to OpenDNS and changed my password - 10 chars UPPER, lower, number and special.  Verified that I could login with that new password - then back to Genie using the new updated password - Same result "The was an error signing in...
 
I see in this thread a response indicating this is a known issue - when might a work around or fix become available?