In response to 0.0.0.0 day, Firefox Nightly version 131 had introduced a new security measure: blocking access to 0.0.0.0/::/::ffff:0.0.0.0 addresses. This change is currently live for Nightly users and will be gradually rolled out to all release users in the near future. Before we implement this ch...
  • @[email protected]
    4•6 hours ago

    That would kill development, because accessing http services locally is something pretty much only developers do. What is the error message?

    • @RedWeaselEnglish
      1•6 hours ago

      Unable to connect

      Firefox can’t establish a connection to the server at 192.168.2.210.

      The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer’s network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox Developer Edition is permitted to access the web.

      I don’t see an error in the log about the specific page I am trying to access, but another had a link to https://support.mozilla.org/en-US/kb/https-only-prefs?utm_source=mozilla&utm_medium=firefox-console-errors&utm_campaign=default&as=u

      • Possibly linuxEnglish
        2•5 hours ago

        I don’t think they ware going to start disabling http. Http is needed in a lot of cases to get https plus there are still use cases for http like testing.

        Have you fired up Wireshark and looked at what port it is connecting to?

        • @RedWeaselEnglish
          1•5 hours ago

          Thanks for the suggestions. While I was investigating I ended up looking and had a proxy issue. Obviously a problem on my part.

      • @RedWeaselEnglish
        1•6 hours ago

        And of course adding an exception or turning it off doesn’t work either.