Ntopng development
-
I have the same problem. It's caused by an error to build the ssl certificate /usr/local/share/ntopng/httpdocs/ssl/ntopng-cert.pem
Thanks, that fixed it.
-
Odd that your CERT doesn't have a new line at the end. Easy enough to fix. Where did the certificate originate from? Was it generated or imported?
-
My CERT is imported.
Where I find it in PFSense to add newline?Thanks
-
Unfortunately once a cert is imported, you cannot edit it. You can edit CAs, but not certs.
-
Odd that your CERT doesn't have a new line at the end. Easy enough to fix. Where did the certificate originate from? Was it generated or imported?
I imported mine as well. Certificate works fine on the pfSense WebGUI
Unfortunately once a cert is imported, you cannot edit it. You can edit CAs, but not certs.
When importing a certificate into pfSense, the key and the certificate are pasted into separate form fields, so if the new line is skipped, it would be something to do with the way pfSense processes the data.
-
pfSense takes the pasted data exactly as is, so it means that the certificated when pasted didn't end in a newline. What you would see in the input box is that after the paste the cursor is at the end of the line that says "–---END CERTIFICATE-----" rather than on the next line.
My guess is that the certificate originated on a Windows system which sometimes omits the newline on files.
-
A PR has been created.
-
Version 0.8.4_4 has the fix for the missing newline at the end of the certificate.
-
I have the same problem. It's caused by an error to build the ssl certificate /usr/local/share/ntopng/httpdocs/ssl/ntopng-cert.pem
If you edit this file you have to change line between the certificate and the private key from
–---END CERTIFICATE----------BEGIN PRIVATE KEY-----
to
-----END CERTIFICATE-----
-----BEGIN PRIVATE KEY-----So you have to add the newline with enter key.
Now works fine.
This tip save my day!!! :D
Thanks!!!!
-
Version 0.8.4_4 has the fix for the missing newline at the end of the certificate.
Yes!!! This new update fix missing newline at the end of the certificate.
Thanks!!
-
Hey polcape, kesawi, can you let me know if your problem is resolved after you install 0.8.4_4 please? Thanks.
-
Hey polcape, kesawi, can you let me know if your problem is resolved after you install 0.8.4_4 please? Thanks.
Problem resolved, thanks for your quick response.
-
I confirm! Problem resolved!
Thanks for quickly fix!
-
Could someone please get the ntopng setup to parse IPv6 addresses too.
I can cludge it by adding my IPv6 addresses to ntopng.sh but every time i go into the noting settings it just resets the values to my IPv4 addresses.
-
-
I was able to get mysql historical data to work.
I've been able to get ntopng to log data to MySQL for the LAN interface, but it didn't read any of the data back until I relocated the database on my NAS from the HDD array to the SSD array as the HDD was too slow to respond the the queries.
Only LAN is keeping historical data. Not sure why but my other interfaces are vlans so that may have something to do with it. Needs more testing to confirm.
I modified the /usr/local/pkg/ntopng.inc file to manually specify the interface for the NIC rather than the VLAN. All of my internal VLANs run through lagg0, so by changing the start up option as below it captures all VLANs on the lagg0 interface and allows me to then bring up global stats or those related to the specific VLAN I'm interested in.
$start .= "\t/usr/local/bin/ntopng -d /var/db/ntopng -G /var/run/ntopng.pid -e {$disable_alerts} -i lagg0 {$dump_flows} {$dns_mode} {$aggregations} {$local_networks} &\n";It would be great if the pfSense ntopng Settings could be updated to allow the underlying interface to be specified if VLANs are being used, and allow mysql settings to be entered from the webGUI.
I've also been playing around with the -S local command line option to see if local hosts can be cached longer so that I can investigate specific hosts that may have been inactive for a little while. It would be good if this could be added as a configurable option in the webGUI as well.
-
I can't log into the webgui anymore under Chrome on Windows- the login button grays out as soon as I enter the second character of the password. It's works fine on Edge. Is anyone else having that problem?
-
Does this package still have a maintainer? Is the development still in progress?
-
I can't log into the webgui anymore under Chrome on Windows- the login button grays out as soon as I enter the second character of the password. It's works fine on Edge. Is anyone else having that problem?
This has been found to be the Chrome RegEx issue that has plagued other parts of pfSense as well. A fix has been found, but hopefully the issue will be fixed in a future version of Chrome. See the link below for how to fix the ntop login page to work again in the meantime:
https://forum.pfsense.org/index.php?topic=119163.msg660247#msg660247
-
Hello,
Can be possible in a future version could activate the pro features?
Or two editions for install.
Because the html reports could be userful for me and other people.Thanks
