Issue metadata
Sign in to add a comment
|
can't connect to my router https://192.168.1.66
Reported by
alinxcra...@gmail.com,
Nov 28 2016
|
||||||||||||||||||||||||
Issue description
Chrome Version : 42.0.2311.90
OS Version: 6.3
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5:
Firefox 4.x:
IE 7/8/9:
Is the same situation on Ubuntu and on Windows for last versions of Google Chrome 64 bit for both OS.
What steps will reproduce the problem?
1.
2.
3.
What is the expected result?
What happens instead of that?
Please provide any additional information below. Attach a screenshot if
possible.
UserAgentString: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.90 Safari/537.36
,
Nov 29 2016
You seem to be running very old chrome version. Could you please upgrade to the latest stable and confirm if the issue still persists. Thank you!
,
Nov 29 2016
Hi, Using: Version 54.0.2840.100 (64-bit) on Linux Version 54.0.2840.99 m (64-bit) on Windows Also gmail says that the browser is not supported any more... Maybe it could be because the cookies are blocked at all from Chrome settings, but I let them to be set for router connection, checked if there are any cookies blocked for the router https connection, and no, there are not... Or maybe it could be from umatrix, ublock origin or flashcontrol? But I tried also in incognito mode with them disable for incognito mode, and still doesn't work. umatrix has all the Privacy settings on, deleting many cookies, and preventing many things. A few hours ago, after I clicked on the triangle next to https:// and after that details, it openel the details, and in the sample window from the left side it instantly worked, closed the derails window, and it really worked in the normal window, and I could navigate through the router settings. I closed that tab and opened another one to see if it will work, and even after opening the details, no, it didn't work again... Firefox, last version still can connect to the router. Thank you.
,
Nov 29 2016
Your net-internals log seems to be captured after attempting to load the page. Could you get a new log by *first* opening net-internals, *then* reproducing the problem? Thanks! (net-internals only records things from when it's open.)
,
Nov 29 2016
,
Nov 29 2016
Thanks! Okay, this looks like the same as issue #488043. This is going to be fun to fix... mmenke and I have a plan that'll be less of a mess than my previous thoughts, but I'll need to write it up and see how messy it'll be. (Why does your router expose an HTTPS interface with a self-signed certificate? This seems kind of pointless.) Anyway, merging into the other bug.
,
Nov 29 2016
I chose https for the router, it is not more secure like that ? Thank you.
,
Nov 29 2016
Tell me please, what I have to do to find out when the issue will be resolved, to try again, see if it will work for me also. Thank you.
,
Nov 29 2016
If you're using a self-signed cert / clicking through the security warning, it's no more secure - that security warning could come from an attacker, you have no way of knowing. That's the whole point of the warning.
,
Nov 29 2016
This bug got merged into issue #488043. I believe you should have been automatically subscribed to it, so you'll get updates on that bug. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by alinxcra...@gmail.com
, Nov 28 2016