You are not logged in.
Not sure if this belongs in the Apps forum or this one, let me know if this doesn't belong here.
On my laptop, I connect to various Wifi networks at hotels, client networks, etc. Most of those Wifi networks have an "accept" or "enter your room #" type page where you must enter some information before the "real" connection is established.
The problem is that Chromium just sits and never connects to this intermediate page, whereas Firefox does. Once I have entered the information on the Firefox side, Chromium works fine. Is this a DNS problem, a Chromium issue or something else? The problem is that there is never any errors displayed on the Chromium side, it just sits indefinitely and never connects.
I don't think this should make a difference, but I use netctl for network management.
Last edited by twelveeighty (2014-03-13 13:40:54)
Offline
Are you using any tools that try to force the use of https when it is available? Like https everywhere ?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
No, not using https everywhere. I do have my Chromium "signed in" so I can sync my bookmarks between phone and browser, so maybe it's hanging on trying to sign in the browser. I haven't tried yet to launch "chromium --incognito", which should prevent any type of sign-in. I'll post back with results.
Edit: sure enough, running chromium --incognito works.
Last edited by twelveeighty (2014-03-13 13:39:42)
Offline