Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    V2.6.0 browser cookies warning loop

    Scheduled Pinned Locked Moved General pfSense Questions
    6 Posts 4 Posters 1.2k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      ComplexNurd
      last edited by

      We are getting an odd issue with the latest V2.6.0. When logging in for the first setup we are unable to get past the login screen. Multiple browsers but the same issue.

      We enter the default username admin and password pfsense but continually get "This browser must support cookies" loop. Same issue on all browsers, cookies enabled, IP address in the exceptions / trusted list, 2 different laptops have been tried. I have only seen this pop up on the new 2.6.0.

      It will end up being something silly but has anyone else having the same drama?

      N 1 Reply Last reply Reply Quote 0
      • jimpJ jimp moved this topic from Problems Installing or Upgrading pfSense Software on
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        Hmm, never seen that.

        Have you tried multiple OSes to connect from?

        It's definitely the pfSense login screen you're seeing?

        Was this after upgrading to 2.6 or a clean install?

        Steve

        1 Reply Last reply Reply Quote 0
        • N
          nimrod @ComplexNurd
          last edited by nimrod

          @complexnurd

          I saw this same scenario on non pfSense router. It turned out that free antivirus solution that was installed on the system has "malicious cookies protection system" that overrides the browser setting and prevents me from logging in. After disabling that "feature" in AntiVirus settings, i was able to access web interface with no cookie warning. So check if you have something like that installed.

          1 Reply Last reply Reply Quote 0
          • C
            ComplexNurd
            last edited by

            @stephenw10 yep defo the fresh pfsense just installed connecting via the LAN address. Both devices connecting were win10, with 4 different browsers tried on each.

            @nimrod haven't tried that yet but will look into it. Just odd as we have loads of PfSense CE VMs and PfSens PLUS hardware boxes out there and I don't recall ever being prompted about cookies before and have never gotten into some strange looping issue.

            Rebooted the server and it has now let us in with no drama but we have done that on a several occasions and it made no difference then, factory reset the pfsense before also with no change.

            Just a bit odd and I was thinking something might have changed in this latest 2.6.0 release. I will keep an eye on it in the lab to see how it goes but it will be in production soon. With this release being so fresh and all......

            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              Yeah always suspicious when you see something after an upgrade but I think it is a coincidence in this case.

              Steve

              1 Reply Last reply Reply Quote 0
              • G
                garry
                last edited by

                I have a new, clean install of 2.6.0 CE that is doing the same thing as the OP described.

                I'm running this box in a VMWare environment. Initial install went normal, with no issues. The issue started when I went into System->Advanced and tried to tell the webConfigurator to use HTTPS. I'm using the default self-signed certificate. The WebGUI redirect box is unchecked (default) and the Anti-lockout is enabled (default). As soon as I click the Save button it breaks the webConfigurator. Every browser gives the message "This browser must support cookies". I have also tried multiple browsers from multiple machines with different OS's. The only way to regain access is to use the console and re-enter the LAN static IP. During that process it asks if the webConfigurator should be reset, choose Y and it resets back to HTTP access only and access is regained.

                Has anyone found why this is happening?

                1 Reply Last reply Reply Quote 1
                • First post
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.