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

[SOLVED] ntopng can't load the page

General pfSense Questions
6
27
21.4k
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 Oct 29, 2016, 12:32 AM Oct 27, 2016, 5:16 PM

    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 Oct 27, 2016, 5:37 PM

      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 Oct 28, 2016, 11:12 AM

        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!

        pfsense-ntopng.jpg
        pfsense-ntopng.jpg_thumb

        1 Reply Last reply Reply Quote 0
        • V
          viragomann
          last edited by Oct 28, 2016, 11:26 AM

          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 Oct 28, 2016, 11:36 AM

            Where I can to configure it?

            1 Reply Last reply Reply Quote 0
            • V
              viragomann
              last edited by Oct 28, 2016, 11:53 AM

              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 Oct 28, 2016, 11:58 AM

                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 Oct 28, 2016, 12:26 PM

                  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 Oct 28, 2016, 2:06 PM

                    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 Oct 28, 2016, 2:36 PM

                      @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 Oct 28, 2016, 3:16 PM

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

                        pfsense-ntopng-2.jpg
                        pfsense-ntopng-2.jpg_thumb

                        1 Reply Last reply Reply Quote 0
                        • V
                          viragomann
                          last edited by Oct 28, 2016, 3:44 PM

                          Again: https://192.168.1.1:3000
                          !

                          1 Reply Last reply Reply Quote 0
                          • G
                            gustavo4001
                            last edited by Oct 28, 2016, 4:10 PM

                            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 Oct 28, 2016, 4:20 PM

                              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 Oct 28, 2016, 4:40 PM

                                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 Oct 28, 2016, 5:00 PM

                                  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 Oct 28, 2016, 5:21 PM

                                    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 Oct 28, 2016, 5:29 PM

                                      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 Oct 28, 2016, 10:03 PM

                                        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
                                        • P
                                          ptt Rebel Alliance
                                          last edited by Oct 28, 2016, 10:09 PM

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

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