Bug #11530
open
ntopng 4.2 needs to be updated to 4.3, Bug when accessing a host for details
Added by Max D over 3 years ago.
Updated about 2 years ago.
Affected Architecture:
amd64
Description
On pfsense 2.5, installing ntopng from package manager ntop 0.8.13_9 which is 4.2 version of ntopng, after logging into ntopng, results in a corrupt web page when clicking on a host for details, this has been fixed in 4.3 by ntopng team.
I installed 4.3 manually from ntopng pfsense doc, and confirmed this resolves the issue.
upvote for this.
P.s. Also don't know what happen with pfsense repo, but installing ntopng from scratch with version of package 0.8.13_10 which should install ntopng-4.2.d20210309,1 - actually install ntopng Community v.3.4.0 at 24/11/2021, previously there was no such bug and I hav 4.2.0 version.
I'll have to spin up a 2.5.2 install of CE to test this, but pfSense CE 2.6.0 includes ntopng-5.0.d20210923,1, so should be fixed in the current unreleased version of CE.
- Status changed from New to Feedback
Tested on pfSense CE 2.5.2. Unable to reproduce. I installed, enabled, and went to the ntopng web interface. After selecting Hosts and selecting a host's details page it loaded without issue on ntopng 4.2. Marking this redmine as Feedback as I don't see this as reproducible. If I'm missing a step please update this redmine with the relevant information.
I can reproduce this in VMs for both 2.5.2 and 2.6. I don't think the new 5.0 package for ntopng solved this and I think it's something to do with how pfsense starts the service after a reboot.
Further, I think the inconsistent bug reporting stems out of how ntopng being started affects whether or not this occurs.
If started automatically after a reboot of pfsense the flows or host page will throw an error.
If you restart the ntopng service it is fixed.
For months now the workaround for me has just been to restart the ntopng service.
I am happy to provide more information but am not sure what to provide.
Sish Kitane wrote in #note-4:
I can reproduce this in VMs for both 2.5.2 and 2.6. I don't think the new 5.0 package for ntopng solved this and I think it's something to do with how pfsense starts the service after a reboot.
Further, I think the inconsistent bug reporting stems out of how ntopng being started affects whether or not this occurs.
If started automatically after a reboot of pfsense the flows or host page will throw an error.
If you restart the ntopng service it is fixed.
For months now the workaround for me has just been to restart the ntopng service.
I am happy to provide more information but am not sure what to provide.
Sish,
Can you check your System logs on your particular instance running 2.6 and provide any relevant error messages regarding startup? I have to believe there is a logged message somewhere regarding the failed startup. May be a startup ordering issue where certain dependencies aren't ready yet.
- Status changed from Feedback to Incomplete
Hello,
Due to lack of response here and the fact that the package was updated to 5.2 in the 22.05 pfSense Plus repos, I'm marking this as incomplete due to lack of information.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by