Navigation

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

    [SOLVED] ntopng can't load the page

    General pfSense Questions
    6
    27
    16325
    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.
    • G
      gustavo4001 last edited by

      Dear,
      I have a pfSense computer installed with IP 192.168.1.1. I installed the "ntopng" package because I need to measure Internet traffic each IP of my LAN.
      ntopng settings: I have marked Enable ntopng and I entered and repeated password is requested. Then I gave SAVE. But when trying to access ntopng remains waiting and waiting until he tells me I spend too much time and the page can not be loaded. The URL that is set in the address bar is 192.168.1.1:3000, I manage pfsense with Firefox through the direction of the PC pfSense is 192.168.1.1 then it seems to use ntopng need to change port and passes this . Can anyone help me with this problem? Thank you.

      1 Reply Last reply Reply Quote 0
      • V
        viragomann last edited by

        This issue should be postet here https://forum.pfsense.org/index.php?board=39.0

        Ensure that pfSense allow access to 192.168.1.1:3000 on the appropriate interface. Maybe you have to add a firewall rule for that.

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

          Dear, to give clicking the link is a list of topics where I have not found a related topic. However I have applied his suggestion and the problem persists. Attachment JPG screenshots. Thank you!


          1 Reply Last reply Reply Quote 0
          • V
            viragomann last edited by

            Since you have configured your pfSense to allow only access via https you have also to access ntop via https. So try https://192.168.1.1:3000

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

              Where I can to configure it?

              1 Reply Last reply Reply Quote 0
              • V
                viragomann last edited by

                What? Just try https://192.168.1.1:3000 instead of http://192.168.1.1:3000

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

                  Ahh Ok… I tried with both http and https but the problem persist  :( ... I am thinking ... if I changed pfSense for use it with http (no https)? Where I could to configure it? it is possible?

                  1 Reply Last reply Reply Quote 0
                  • V
                    viragomann last edited by

                    In System > Advanced > Admin Access. But this will make no difference.

                    Just seen your WAN IP is 192.168.1.1.  So have you unchecked "Block private networks" in the interface settings?

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

                      My WAN IP don't is 192.168.1.1, so 192.168.1.1 is my LAN IP. WAN IP and W2 IP are static IPs provide by my ISP… for LAN IP and WAN IP and W2 IP I have unchecked Block private networks

                      1 Reply Last reply Reply Quote 0
                      • V
                        viragomann last edited by

                        @gustavo4001:

                        My WAN IP don't is 192.168.1.1, so 192.168.1.1 is my LAN IP.

                        So you've set the rule for accessing pfSense on the wrong interface.
                        Open the rule and change the interface to LAN.

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

                          I corrected it, but problem persist, see you new jpg attached on bottom image …


                          1 Reply Last reply Reply Quote 0
                          • V
                            viragomann last edited by

                            Again: https://192.168.1.1:3000
                            !

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

                              For I do fast I copy and paste only botton jpg, but I tested for both way, http://192.168.1.1:3000 and https://192.168.1.1:3000 don't works, same problem

                              1 Reply Last reply Reply Quote 0
                              • V
                                viragomann last edited by

                                I see. So edit the rule allowing the access and enable logging.
                                Also enable logging of the default block rule in Status > System Logs > Settings.

                                Then check the firewall logs for entries relating to the access to 192.168.1.1:3000.

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

                                  I enabled logs for the rula and enabled logs of default block rule. No traces for 192.168.1.1 , but yes traces for rest IPs of my LAN. I think no problem of firewall, could be IIS of pfSense is stopped? I unknow I am thinking…. :-\

                                  1 Reply Last reply Reply Quote 0
                                  • V
                                    viragomann last edited by

                                    That makes no sense. Since your are able to access the Web GUI at 192.168.1.1 from a PC you should also be able to access 192.168.1.1:3000 as long as there is no other device between the PC and pfSense which block that.

                                    Albeit if ntopng isn't working you must see the access in the firewall logs.

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

                                      Now I have a great problem. I was to advanced configuration and I changed pfSense protocol to HTTP (it was setted in HTTPS). So I closed the browser, but when I try open now http://192.168.1.1 it wait… waut and not load!!!!!!! go by timeout... Also when display timeout automatically it change URL to https://192.168.1.1  :-[

                                      1 Reply Last reply Reply Quote 0
                                      • V
                                        viragomann last edited by

                                        The only quick idea I have to this, you can set it back to https in the console interface.
                                        Go through the LAN address setting, set the IP and mask again. At the end of this you will be ask if you want to allow access via https.

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

                                          Finally I solved webConfigurator access enter by 8) Shell in console and editig /conf/config.xml , so I have put <protocol>https</protocol> so I restart and it works, by some cause it works only with with https, so I think it is root of the problem ntopng not load , it still persist

                                          1 Reply Last reply Reply Quote 0
                                          • ptt
                                            ptt Rebel Alliance last edited by

                                            ??? What about squid/squidGuard, maybe they are related to the issue ?

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

                                              I suspect it, but I review configuration and not seen strange thing, I have 2 pfSense in 2 disticts phisical LAN, recently I seen other pfSense in other LAN (distinct phisical location) allow use protocol http so I installed ntopng package and IT WORKS!!!! … so I must solve in first LAN something of configuration I think because there is still the problem persists and I think because not can use http protocol

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

                                                Finally I have gotten it to work! … I does next steps: 1) Reconfigure webgui protocol with http and port 80 (back I not have put 80, only http) ; 2) Restart pfSense and it works! ; 3) I erased package ntopng ; 4) Restart pfSense ; 5) I installed again package ntopng ; 6) Restart pfSense ; 7) All works!!!!! thank you very much for your interest in my problem!

                                                1 Reply Last reply Reply Quote 0
                                                • A
                                                  aeleus last edited by

                                                  Just reboot pfsense after installing and configuring ntopng.

                                                  I just installed ntopng 0.8.6_1 on pfsense 2.3.3-RELEASE-p1.

                                                  ntopng times out

                                                  Restarted the ntopng service - still times out.

                                                  Reboot the pfsense server - ntopng now works.

                                                  No configuration changes or firewall rules required.

                                                  1 Reply Last reply Reply Quote 0
                                                  • U
                                                    uberwebguru last edited by

                                                    ntop still wont work even after restarting pfsense
                                                    this is not solved

                                                    anyone else having this problem?

                                                    using pfsense 2.4.4-RELEASE-p1

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

                                                      So you are seeing exactly the same symptoms?

                                                      You should update to 2.4.4p2 but that's probably unrelated.

                                                      Steve

                                                      U 1 Reply Last reply Reply Quote 0
                                                      • U
                                                        uberwebguru @stephenw10 last edited by uberwebguru

                                                        @stephenw10 said in [SOLVED] ntopng can't load the page:

                                                        So you are seeing exactly the same symptoms?

                                                        You should update to 2.4.4p2 but that's probably unrelated.

                                                        Steve

                                                        i did update to 2.4.4-RELEASE-p2 now and still same problem..i have restarted ntoppng and even pfsense and the server..still no show
                                                        https://forum.netgate.com/post/832233

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

                                                          Locking this. If you're seeing some problem with ntopng it's clearly unrelated to whatever issues existed in 2016! I have run ntop without issue many times since then. Please open a new thread detailing exactly what you have tried and what is not working.

                                                          Steve

                                                          1 Reply Last reply Reply Quote 0
                                                          • First post
                                                            Last post