02-16-2012 10:12 AM - edited 02-16-2012 10:13 AM
I was unable to access the web admin on my WRT160n v3 w/ latest firmware this morning. Reset config to defaults & was able to get in. Enabled HTTPS access & disabled HTTP access & was right back where I started; reset to defaults again & left both boxes checked. Can access via HTTP, but HTTPS requests get refused/reset.
The reason I needed access was that when I booted up my laptop this morning, my wireless card wasn't picking up an IP address via WIFI, only worked via ethernet, so I need to see what was going on there — several reboots of the router didn't fix, nor has it fixed the HTTPS access problem described above.
02-16-2012 11:40 AM
I am having this same issue with an E1000 router. Just started fairly recently. I just posted, here in the forums, regarding it. HTTPS access is not working at all for me. I had to reset the router and go through and reapply all my settings but change the Local Management Access back to HTTP. Works fine with HTTP and I saved this config. If I change it to HTTPS, though, I completely lose access, again, and have to reset the router and apply the HTTP config. So, seems we are having the exact same issue.
02-16-2012 01:00 PM
Ah. See, here:
Same issue. I thought it might be due to a MS update. Apparently so.
02-16-2012 01:33 PM
I've tested this on both a Windows XP machine and a Mac (OS X Lion), so it's not an OS issue. Originally did not test in any browsers other than Chrome. I did just test in Firefox & Safari on Windows & they do not reproduce the problem — HTTPS ok in FF & Safari.
So, this appears to be a Chrome compatibility issue. (Note: clearing cookies doesn't help).
02-16-2012 01:35 PM
Thanks for the response.
So, maybe it is a different issue for me. I am fairly certain I am having the same issue described in the link I posted, above.
02-24-2012 07:16 PM
I have swicthed to https and can no longer access my router.
What port should be specified when using https?
05-02-2012 10:56 AM
I am having the same issue with my WRT160n v3. I just upgraded the firmware to v3.0.03 and the issue is not resolved. It's been almost 2 yrs since a new firmware upgrade has been available. I wouldn't hold your breath to see a fix at this time.