Elektrine lite

← Feed

@caten@mathstodon.xyz

Post #1183944

2026-04-14 18:28 UTC

Does anyone know how to make this patronizing warning go away in #Librewolf? I have to suffer through this every time I want to visit a local address, and I don't want to just start manually adding all the addresses I visit. I'd just like to turn the thing off completely. If I can figure this out, I might try to do the same for the "no HTTPS" warning. #WebBrowser #HTTPS #HTTP #web #internet #Firefox #networking #security #Mozilla

Replies (4)

  • @caten@mathstodon.xyz I took a look and I don't see a quick way to turn it off inside of settings. There is a whole page about creating overrides. Maybe a script there can help. Within about:config you can search for https and look for dom.security.https_only_mode_ever_enabled. Try turning the value to false. Restart. It should give you the options in settings to turn it off and on as you wish.

    Open ##2422439

  • @kepstin@tenforward.social 2026-04-14 23:09

    @caten@mathstodon.xyz In upstream Firefox, clicking the "Proceed to…" button saves an exception for that site, meaning you should only ever see this warning once for any given site. I don't believe there is any way to disable this warning in general (doing so would make https certificate validation ineffective). If you are running a large number of different local sites, you could consider setting up a private certificate authority and adding it to your system trust store (or just Librewolf, depending on use case). The browser should then automatically trust the certs signed by that CA used by your local sites. (If you own a domain name, you could also get "real" free letsencrypt certs for local servers using dns validation). Regarding the "no https" warning - check what you have the "https only mode" option set to under about:preferences#privacy ? There's also some tweaks in about:config if you search for `dom.security.https_only` tho I'm not sure what they all do. Weird things can also happen regarding https if some service has set the Strict-Transport-Security header when you didn't expect it to.

    Open ##2422442

  • @Lilyana@tech.lgbt 2026-04-14 23:10

    @caten@mathstodon.xyz This is why I don't use HTTPS on anything local.

    Open ##2422445

  • @annika@xoxo.zone 2026-04-15 06:33

    @caten@mathstodon.xyz It says "unknown issuer," is this a self-signed cert? Could you import the cert (or its CA) into your browser's cert database and trust it?

    Open ##2422450