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

    pfSense web GUI very slow load on home page

    Scheduled Pinned Locked Moved General pfSense Questions
    25 Posts 6 Posters 20.9k 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.
    • johnpozJ
      johnpoz LAYER 8 Global Moderator @tantan5e
      last edited by johnpoz

      @tantan5e said in pfSense web GUI very slow load on home page:

      we have a Windows AD environment/DNS server that handles all of the resolution. The AD DNS servers are what I have in the pfsense box.

      If your an AD shop your clients should be pointing to your AD, they should get their dns from that, and this should be your dhcp as well.

      If you want to point your AD dns to pfsense so it can resolve that works, or you can just forward or resolve from your AD dns as well.. Pointing clients to pfsense for dns, just so it can go ask your AD dns doesn't make a lot of sense.

      Just let pfsense resolve!! out of the box for the stuff it needs too.. And if you want it to be able to resolve IPs in your network, then create a domain override pointing to your AD dns so you ca do the PTRs, etc..

      Your gui is prob slow because to pfsense dns is not working - or is very slow!!!

      An intelligent man is sometimes forced to be drunk to spend time with his fools
      If you get confused: Listen to the Music Play
      Please don't Chat/PM me for help, unless mod related
      SG-4860 24.11 | Lab VMs 2.8, 24.11

      1 Reply Last reply Reply Quote 0
      • bmeeksB
        bmeeks
        last edited by

        @johnpoz is correct. The slow GUI is most likely caused by DNS resolution difficulties on the firewall. For what it's worth, when testing things in virtual machines in the past (like switching from Forwarder to Resolver or back and forth) I've had to reboot the firewall to get things working well. Granted that was with some older pfSense versions, but if you have not rebooted the firewall it would not hurt to try that.

        T 1 Reply Last reply Reply Quote 0
        • T
          tantan5e @tim.mcmanus
          last edited by tantan5e

          @tim-mcmanus

          So her is what my config looks like, I have the DNS blocked out but what I have in there is my AD DNS servers
          b9d27419-6f35-4a6c-b669-307686861e0b-image.png

          DNS Forwarding is unchecked
          9a3a6fca-e34a-4244-8f5b-c2a21f4ce754-image.png

          af7db702-fb8a-4759-b04f-2030742eccaa-image.png

          Thank you for the reply and the help but it looks like based off your feed back everything seems to be set correctly for my AD environment.

          T 1 Reply Last reply Reply Quote 0
          • T
            tantan5e @bmeeks
            last edited by

            @bmeeks Ok thank you for that, I am pretty sure I have done a reboot on it since the issue started but I am not sure, I will try to do that at the end of the day. Thank you.

            1 Reply Last reply Reply Quote 0
            • T
              tim.mcmanus @tantan5e
              last edited by tim.mcmanus

              @tantan5e said in pfSense web GUI very slow load on home page:

              @tim-mcmanus

              Thank you for the reply and the help but it looks like based off your feed back everything seems to be set correctly for my AD environment.

              Not exactly. pfSense is still resolving DNS since you have the resolver running. Disable it and see if it makes a difference.

              Also, the way you have the resolver set up, it's listening for DNS queries on all interfaces, including your WAN. You'll notice in my screen shots that I only resolve DNS internally.

              T 1 Reply Last reply Reply Quote 0
              • T
                tantan5e @tim.mcmanus
                last edited by

                @tim-mcmanus

                OK I will uncheck the enable DNS resolver here and see if that helps.

                1 Reply Last reply Reply Quote 0
                • bmeeksB
                  bmeeks
                  last edited by

                  You do not want to check the box that says Disable DNS Forwarder on the GENERAL SETUP screen. Since you are running DNS Resolver, you may as well let pfSense use it to perform external lookups for the firewall itself.

                  It may be that your internal AD servers are having issues resolving the pfSense update services. Unusual if that is the case. Try unchecking that checkbox I mentioned, save and apply the changes and then reboot the firewall for good measure.

                  T 1 Reply Last reply Reply Quote 0
                  • T
                    tim.mcmanus
                    last edited by

                    One last question that may seem obvious, but I have to ask it. Your FQDN in your DNS server for your pfSense installation is: pfSense.ad.purgrips.com

                    Is that the correct FQDN entry in your DNS server?

                    1 Reply Last reply Reply Quote 0
                    • T
                      tantan5e @bmeeks
                      last edited by

                      @bmeeks That is what it is, thank you very much for your help there, I was wondering about that but I was a little nervous to uncheck that but that fixed it. Thank you for your help.

                      bmeeksB 1 Reply Last reply Reply Quote 0
                      • bmeeksB
                        bmeeks @tantan5e
                        last edited by bmeeks

                        @tantan5e said in pfSense web GUI very slow load on home page:

                        @bmeeks That is what it is, thank you very much for your help there, I was wondering about that but I was a little nervous to uncheck that but that fixed it. Thank you for your help.

                        Glad it's fixed for you. That box tells pfSense whether or not it should use its own internal DNS server for lookups or if it should only forward everything to the server (or servers) configured in the DNS box. In your case, with the box checked, pfSense would be trying to get your internal DNS servers to do all the lookups instead of using the DNS Resolver built into pfSense. For some reason forwarding is not working correctly. Your internal DNS servers should be able to resolve the pfSense update services if they can resolve other external web sites. You may still want to investigate why that is.

                        1 Reply Last reply Reply Quote 0
                        • B
                          BBQigniter
                          last edited by

                          I'm very sorry for resurrecting this thread - but this thread is mostly the first hit you find if you google for something like "pfsense slow login" or "slow dashboard" and for me it initially did not help, checking my DNS-settings.

                          after hours looking for a solution I stumbled over this reddit post - https://www.reddit.com/r/PFSENSE/comments/lmubku/comment/gtj41yl/?utm_source=share&utm_medium=web2x&context=3

                          disabled "firewall logs" widget - and dashboard now loads fast and login is also fast. The strange thing is, that I have another machine with a virtual pfsense installed (pretty much same hardware - cpu, ram, disk) and had the dashboard equally configured (and mostly all other settings are equal too) where this long loading issue did not happen.

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