We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Sök i support

Akta dig för supportbedrägerier: Vi kommer aldrig att be dig att ringa eller skicka ett sms till ett telefonnummer eller dela personlig information. Rapportera misstänkt aktivitet med alternativet "Rapportera missbruk".

Läs mer

Untrusted connection on connecting to Wifi - no way to get past

  • 3 svar
  • 7 har detta problem
  • 4 visningar
  • Senaste svar av ncsmall

more options

I am very familiar with the Advanced option on getting this connection message which allows you (on the desktop) to connect anyway ("I understand the risks") and / or create an exception. This does not seem to exist in the Android product. I am running the latest version on Android 6.0.1. When I connect to Wifi at, e. g. a coffeeshop. the Untrusted Connection message appears and there is only one option, namely "Get me out of here". There seems to have been an add-on set-cert-except that would have got around this but it no longer seems to exist. As a result, in order to connect on public Wifi, I have to open Chrome, connect, then exit, then start Firefox. Which is an annoyance. Is there a way around this ?

I am very familiar with the Advanced option on getting this connection message which allows you (on the desktop) to connect anyway ("I understand the risks") and / or create an exception. This does not seem to exist in the Android product. I am running the latest version on Android 6.0.1. When I connect to Wifi at, e. g. a coffeeshop. the Untrusted Connection message appears and there is only one option, namely "Get me out of here". There seems to have been an add-on set-cert-except that would have got around this but it no longer seems to exist. As a result, in order to connect on public Wifi, I have to open Chrome, connect, then exit, then start Firefox. Which is an annoyance. Is there a way around this ?

Vald lösning

If you are connecting to WiFi with a "captive portal" visit a site that does not use https by default. News sites are a decent choice, I tend to use http://www.bbc.com or http://cnn.com

It is not possible or safe for Firefox to ignore this issue. The best it can do is to detect that you are on a captive portal, pause tab loading and open a new tab to reach the captive portal login/authorization page. This is being added to desktop Firefox soon, depending on how the change was made Firefox for Android may get the feature for free.

Läs svaret i sitt sammanhang 👍 5

Alla svar (3)

more options

Vald lösning

If you are connecting to WiFi with a "captive portal" visit a site that does not use https by default. News sites are a decent choice, I tend to use http://www.bbc.com or http://cnn.com

It is not possible or safe for Firefox to ignore this issue. The best it can do is to detect that you are on a captive portal, pause tab loading and open a new tab to reach the captive portal login/authorization page. This is being added to desktop Firefox soon, depending on how the change was made Firefox for Android may get the feature for free.

more options

Thanks for the reply. The issue with, e. g. coffee shop wifi, is that it will not let me connect to anything, http or https, without first connecting to the portal. I can choose not to connect to the portal, of course, but then I am using my data plan, which again defeats the purpose of connecting to public wifi. So there is no other solution ? Why is it ok for desktop Firefox to allow for exceptions but not Android ?

more options

Actually, much to my surprise, this worked; thank you, and apologies for the earlier post. I had had the home page set to google and did not realize the https: status did make a difference to the initial connection, for Firefox if not for the other browsers. As soon as I set the home page, as you suggested, to a news site, it worked fine (had to go out and test it at the coffee shop to make sure !) Other difference between Firefox and the other browsers on startup is that the application needs to be completely closed beforehand in order to try to connect to the home page on startup. With Chrome, for example, it is only necessary that no Chrome browser windows be open. Thanks for the help Charles