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

    Lihttpd error after upgrade from 2.0.1 to 2.0.3

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    14 Posts 3 Posters 4.6k 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.
    • M
      mj
      last edited by

      that is what i understood.

      It is still logging the error every 2 seconds.

      Nothing that i can find is trying to connect http to the GUI.

      Is it possibly a package I installed that is causing this?

      1 Reply Last reply Reply Quote 0
      • W
        wallabybob
        last edited by

        @mj:

        Nothing that i can find is trying to connect http to the GUI.

        How did you look?

        @mj:

        Is it possibly a package I installed that is causing this?

        What packages do you have installed?

        Please post a screenshot of GUI parameters as set on System -> Advanced, Admin Access tab.

        1 Reply Last reply Reply Quote 0
        • M
          mj
          last edited by

          @wallabybob:

          @mj:

          Nothing that i can find is trying to connect http to the GUI.

          How did you look?

          I checked connections under Diagnostics/States to see if there was any connections to the firewall on port 80

          @mj:

          Is it possibly a package I installed that is causing this?

          What packages do you have installed?

          Lightsquid

          Open-VM-Tools

          OpenVPN Client Export Utility

          pfBlocker

          squid

          squidGuard

          Please post a screenshot of GUI parameters as set on System -> Advanced, Admin Access tab.

          http://imgur.com/Y8n4CnD

          thanks

          1 Reply Last reply Reply Quote 0
          • W
            wallabybob
            last edited by

            You have the pfSense GUI listening on port 8443 for https. Is that intended?

            1 Reply Last reply Reply Quote 0
            • M
              mj
              last edited by

              @wallabybob:

              You have the pfSense GUI listening on port 8443 for https. Is that intended?

              yes. call me paranoid, but i don't like leaving the GUI on the default port for ssl.
              could this be an issue?

              1 Reply Last reply Reply Quote 0
              • M
                mj
                last edited by

                After changing the GUI port back to default 443,
                the messages stop being logged.

                I will leave it on default, seeing that the system log is usable again

                thanks for the help!

                1 Reply Last reply Reply Quote 0
                • jimpJ
                  jimp Rebel Alliance Developer Netgate
                  last edited by

                  That probably didn't solve anything, it hid the actual problem.

                  Most likely, something like pfBlocker is trying to hit the gui with http://(your ip):8443 in a URL table alias when it should have been https://(your ip):8443

                  Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

                  Need help fast? Netgate Global Support!

                  Do not Chat/PM for help!

                  1 Reply Last reply Reply Quote 0
                  • M
                    mj
                    last edited by

                    hi

                    the error is back again!! aargh.

                    can someone point me in the right direction to trace what is causing this?

                    thanks

                    1 Reply Last reply Reply Quote 0
                    • jimpJ
                      jimp Rebel Alliance Developer Netgate
                      last edited by

                      You'd need to run a packet capture watching for connections to your firewall on port 8443, and see what the source IP of the traffic ends up being there.

                      Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

                      Need help fast? Netgate Global Support!

                      Do not Chat/PM for help!

                      1 Reply Last reply Reply Quote 0
                      • M
                        mj
                        last edited by

                        @jimp:

                        You'd need to run a packet capture watching for connections to your firewall on port 8443, and see what the source IP of the traffic ends up being there.

                        i finally found it was my spiceworks network scanner, that was scanning the pfsense, and causing the error in the logs.

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