[SOLVED] Plugin os-ntopng - starts but Web-GUI not accessible

[thowe]

Hello everybody

I tried installing the os-ntopng plugin from OPNsense yesterday. So not the newly offered one from ntopng itself.

Redis had been installed for a while on my current OPNsense system (OPNsense 20.7.7_1-amd64) and was running fine. The installation of os-ntopng went normally. The service became green.

Before accessing the GUI of ntopng I first looked at the settings of ntopng in the OPNsense GUI and saw under Advanced that you can remove the default value of LAN if you want to configure the interfaces later in ntopng. Then I pressed Save button and restarted the ntopng service.

When I finally wanted to access ntopng GUI (LAN IP of the OPNsense + port number from the settings), the browser turned only to the timeout. The same is true for http and https ports.

I can't exclude that my (premature) removal of the LAN interface on level OPNsense plugin settings led to this problem.

Now I have already uninstalled both redis and ntopng plugins several times, additionally manually deleted the residues (conf, db) from the system and reinstalled the plugins. Unfortunately always with the same success: ntopng seems to run. But I can't reach its GUI.

In order to make a completely fresh installation, do I need to uninstall certain files?

Thanks for any hints. :-)

Output of ntopng restart:

Code: [Select]

# /usr/local/etc/rc.d/ntopng restart
Stopping ntopng.
Waiting for PIDS: 90421.
Starting ntopng.
17/Jan/2021 11:00:52 [Ntop.cpp:2291] Setting local networks to 127.0.0.0/8
17/Jan/2021 11:00:52 [Redis.cpp:162] Successfully connected to redis 127.0.0.1@0
17/Jan/2021 11:00:52 [Redis.cpp:162] Successfully connected to redis 127.0.0.1@0
17/Jan/2021 11:00:53 [Ntop.cpp:2231] Parent process is exiting (this is normal)


[thowe]

Sometimes it's easier than you think. I have searched MUCH too far with my configuration considerations.

Even though it's a bit embarrassing for me, I'm happy to post here what the problem was. In retrospect, I can't believe that I only noticed it now... 

I simply had not created a firewall rule that would allow access to the ntopng port from the LAN. Implicitly I had assumed that such a rule would be created.

After allowing access to the port from the LAN, I also reach ntopng.

Maybe it will help someone.