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

    Ntop not working with 1.0.1

    Scheduled Pinned Locked Moved pfSense Packages
    10 Posts 4 Posters 4.1k 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.
    • H
      hadi57
      last edited by

      any body have the problem of not being able to run ntop on 1.0.1 or it's just me, i have this problem on 3 pfsense boxes.

      1 Reply Last reply Reply Quote 0
      • J
        jeroen234
        last edited by

        how mutch memorie do you have on these pc's ???

        with more then 512 mb memorie ntop must work

        1 Reply Last reply Reply Quote 0
        • Y
          yoda715
          last edited by

          Ntop is working, the issue more than likely is that you are using the https protocol and a non standard port for your webgui.

          To access ntop, change your protocol and port for the webgui back to http port 80.

          I have found the bug that is causing ntop not to work under https, I will have a fix soon.

          Also, make sure you have a rule to allow tcp port 3000 traffic destined to the LAN interface IP.

          1 Reply Last reply Reply Quote 0
          • H
            hadi57
            last edited by

            thanks, ill wait for the fix,  by the way it was working fine on pfsense 1, i have 1 gig memory, not using https, and how to change the web gui port?

            1 Reply Last reply Reply Quote 0
            • Y
              yoda715
              last edited by

              @hadi57:

              thanks, ill wait for the fix,  by the way it was working fine on pfsense 1, i have 1 gig memory, not using https, and how to change the web gui port?

              You can change the webgui port under System>General setup. Make sure that you configure the settings for ntop. Choose a admin password for it as well as select at least 1 interface which includes your WAN if.

              If you're not using a custom port it should be working. Works for me. Anyone else having troubles?

              1 Reply Last reply Reply Quote 0
              • H
                hadi57
                last edited by

                well i don't know what i am doing wrong, i made the same setup as with my version 1 servers.  now all the servers that were updated to 1.0.1 ended up with ntop not working. while version servers of version pfsense are all working.

                1 Reply Last reply Reply Quote 0
                • Y
                  yoda715
                  last edited by

                  The fix has been committed. The next snapshot should have the fix implemented. Only other thing is if you have removed the LAN allow all rule make sure you allow port 3000 to the LAN interface IP.

                  1 Reply Last reply Reply Quote 0
                  • H
                    hadi57
                    last edited by

                    i went to status> services, I found that ntop is not running, i tryed to started, but it wouldnt, so the problem was it is not starting at the 1st place, and still cant figure out why, any clues of what ive done wrong, since i copy the same configure from v1 and restore it to 1.0.1, by the way, my firewall rule is: allow all protocols and any port.

                    thank u for your help

                    1 Reply Last reply Reply Quote 0
                    • Y
                      yoda715
                      last edited by

                      @hadi57:

                      i went to status> services, I found that ntop is not stoping i tryed to started, but it wouldnt, so the problem was it is not starting at the 1st place, and still cant figure out why, any clues of what ive done wrong, since i copy the same configure from v1 and restore it to 1.0.1, by the way, my firewall rule is: allow all protocols and any port.

                      thank u for your help

                      Not sure. Might try reinstalling pfsense without importing your config to see if that has anything to do with it.

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

                        Not sure if this helps, but I had a similar issue that was caused by special characters in the ntop admin password.
                          I have verified that the following special characters do not work: &)=%#!?}]
                          These special characters do work: (^$@~<>{[
                        Those are the only characters I had the time to test.

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