NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Unable to log into http://192.168.100.1 because "Your connection to this site is not private"
I've searched through this community and haven't found a solution that works for me. I saw that a few people (such as, tmbrwolf ) have had the same problem which was solved by resetting the modem - I...
After calling Eero, and then calling Xfinity.. I called Netgear, explained the problem and they opened a case #, then transferred me to technical support. I was on hold for nearly 25 minutes. So, I hung up and called them back (same number I called before). In the meantime, they closed my case # ! Then they gave me a new case #, transferred me to Technical Support *again*. After another 20 minutes, I hung up.
Given what I paid for this new modem and the new Eero router (total over $1,000.00), these hassles are not worth it.
SOLUTION: Returned this modem and the new router to Best Buy for a full refund. For the cost of Xfinity's monthly modem/router rental, I can rent for years.
> Get over it.
Back 'atcha there antinode. Your arrogrant attitude is extremely unhelpful.
Don't bother replying. I'm out of here. Bye!
> Unable to log into http://192.168.100.1 because "Your connection to
> this site is not private"
It's common to get complaints from a modern web browser when you use
the modem/router's management web site, because the browser is worried
about your sending some user credentials over an unencrypted/insecure
link ("http://" instead of "https://"). The easy thing to do is ignore
the warning, and proceed. Presumably, you're talking to your own gizmo
on your own LAN. If someone can overlisten to that local traffic, then
you're already in big trouble.
> I CANNOT GET PAST THE LOGIN WINDOW. [...]
You need to tell your web browser to let you continue using the "not
private" connection. Then you need to specify the correct user name and
password. Specifying bad (including no) credentials leads to that "401"
error.