I can NO LONGER singin to motel networks.
I am a long time (decades) user of Firefox. Over the years you have gradually increased your security measures. I have adapted, two-factor, etc, having no choice. But recently (last 6 months or so) I have been UNABLE to sign into motel networks. There used to be a "accept" option to bypass the security issues mentioned in this write-up. That bypass is no longer available.
We travel a lot for long weekends and this situation, not being able to sign-in and use my computer for a full weekend, is UNTENABLE to me. If you can not fix this problem, I will have NO choice but to end using Firefox and switch to another browser. Chuck
എല്ലാ മറുപടികളും (2)
It is not clear how Firefox enters the equation of signing into guest networks (as that is handled by your device per se) — does this mean the operator requires you to fill some login credentials via a "captive portal" i.e. their interface inside the browser after connecting to their network before allowing any further site to load — and this step fails? Or they don't present any login requirement and any site load then fails? Or you pass the captive portal, and then nothing further loads?
In any case that sounds like a misconfiguration on the network operator side — if they don't know how to make the connection work it would be better if somebody from their side working on it got in touch with Mozilla, ideally file a compatibility bug if they have issues using their network setup, and somebody would be able to assist further.
Unless this is caused by, say, an antivirus or security software on the consumer device, there's not much an end user can influence if the connection is what it is (Firefox is just the recipient, if the response can't be resolved, it can't fix it up on its own).
If you share a full error page you're getting, with all the codes from any "Advanced" section expanded (but realistically it would also need the connection info, certificates as served by which device etc.), somebody could try to assist you further, but without any more details the answer is basically "the browser is not being allowed to establish connections outside" which can have many reasons unfortunately.
(Also, for completeness, there are users that have the "captive portal" detection manually disabled, which in turn then won't automatically trigger the guest network sign in flow — and the service will try to block and/or inject into every response, voiding its integrity if for a secure site. Option one is create a new blank profile on the side and try connecting from that one on factory defaults. Option two is to try to probe the guest wifi using an insecure site as http://httpforever.com/ or http://example.com/ (with the explicit http: scheme, not https: to allow getting the networking stack inject the prompt where necessary).
You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.