3 ms·
I'm highly surprised by this. It seems very dumb and I have never seen anything like this, though I never use Chrome and very rarely fire Chromium for testing s
by jraph 2y ago
I'm highly surprised by this. It seems very dumb and I have never seen anything like this, though I never use Chrome and very rarely fire Chromium for testing something.
Is there something to read about this, like a dev ticket?
- Dylan16807 2y agoThere might be but I'm not aware of any tickets. But if you open chrome and navigate to 192.168.20.20 you should see it. Or any domain that resolves to a non-responsive IP, if you have one in mind.
- jraph 2y agoJust tried on Chromium, I get ERR_ADDRESS_UNREACHABLE as I would expect.
- Dylan16807 2y agoYeah, someone else said it's not enabled for everyone. It might just be settings? Do you have "Always use secure connections" turned on? I don't remember if that was a manual toggle or not. However it's triggered, I hope they make the UI better before they deploy it more widely. And I'll quote the exact text for you: [warning triangle] The connection to 192.168.0.40 is not secure You are seeing this warning because this site does not support HTTPS. Learn more [Continue to site] [Go back] Then when I click continue, the only sign it's doing anything is that the reload arrow becomes a stop X. After 20 seconds it moves on to "This site can't be reached".
- jraph 2y agoYep, indeed I'm seeing this if I enable this option.