NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
averagejohndoh
Jan 11, 2021Follower
routerlogin.net edge browser
I cannot login to routerlogin.net. I only have edge browser and they do not allow http. They require https. So when I put in the username and password it just keeps refreshing the page asking me to put it in again. I tried downloading some genie software from netgear.com for the r6300v2 router and it will not download. It just times out. I tried the nighthawk app and it says it does not support this router. I have no way to get in to my router. Modern browsers will not allow basic authentication of http. Is there any hope or do I go buy a non-netgear router because you guys abandon us.
7 Replies
- ColwlAspirant
averagejohndoh wrote:I cannot login to routerlogin.net. I only have edge browser and they do not allow http. They require https. So when I put in the username and password it just keeps refreshing the page asking me to put it in again. I tried downloading some genie software from netgear.com for the r6300v2 router and it will not download. It just times out. I tried the nighthawk app and it says it does not support this router. I have no way to get in to my router. Modern browsers will not allow basic authentication of http. Is there any hope or do I go buy a non-netgear router because you guys abandon us.
Hi
You can access route by typing its address into the browser url bar. ie 192.168.1.1 > [...] I only have edge browser and they do not allow http. [...]
"do not allow" or "complain about"?
It's common to get complaints from a modern web browser when you use
the router's/extender'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.Worst case: Use a more cooperative web browser.
- wcalifasProdigy
Try www.routerlogin.net or 192.168.1.1
> Try www.routerlogin.net [...]
Have you any reason (evidence, plausible grounds for speculation,
anything at all) to believe that "routerlogin.net" and
"www.routerlogin.net" would be resolved differently?> [...] or 192.168.1.1
Or that specifying an address instead of a name would affect an
"HTTP" v. "HTTPS" difficulty?