[SOLVED] ntopng can't load the page
-
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.
-
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!
-
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
-
Where I can to configure it?
-
What? Just try https://192.168.1.1:3000 instead of http://192.168.1.1:3000
-
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?
-
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?
-
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
-
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. -
I corrected it, but problem persist, see you new jpg attached on bottom image …
-
Again: https://192.168.1.1:3000
! -
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
-
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.
-
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…. :-\
-
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.
-
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 :-[
-
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. -
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
-
??? What about squid/squidGuard, maybe they are related to the issue ?
-
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
