issue accessing ntopng after 23.1 upgrade

[RobLatour]

After upgrading to 23.1 I had/have an issue with accessing ntopng

In the previous version of OPNsense (22.7) I had set up the ntopng service to use a certificate related to duckdns.org

When I sign on to opnsense I use the address:
https://xxxx.duckdns.org/index.php
where xxxx is my duckdns name
this worked fine in the prior version of OPNsense and continues to work fine in 23.1

However, signing on to ntopng using
https://xxxx.duckdns.org:3000
no longer works.

The work-around for now is to use
http://xxxx.duckdns.org:3000
(no 's' after 'http')
and I can connect, but with an unsecured connection.

I am posting this here, but I am not sure if it is an opnsense or an ntopng issue.

Any thoughts?

[mikebutash]

I've not used ntop in a few years since they went more commercial, but moving from my old fortigate to opnsense I am, and find ntop is a bit of a bastard in leaking memory over time.  I gave the box 8gb (I run it inside proxmox), but even though top said it wasn't using memory, observed with snmp it started hitting swap (via librenms polling).  I upped it to 16gb, and while it climbed for the first day or two, plateau'd out in terms of use, but top/htop still report nowhere near the levels of memory use snmp did (and swap when it gets/got there).  Weird, but not terrible.

That said usual troubleshooting applies with getting opnsense and all these plugins working.  Use netstat -4an, make sure the port(s, if ssl) are running, and services are working.  Try restarting ntop via the gui, and if not, check any system logs what is failing.  If you need to, "service ntopng restart" and check logs at "/var/db/ntopng/ntopng.log" (maybe others...), but most of my problems have been related to it just chewing up resources over time to kick it occasionally.  I might just reboot the darn thing via cron once a week to keep it sane, but at least 16gb memory helps.

Using ntop for some ~20 years, it's never without challenges, but often worth it, and a great pairing with opnsense since not needing to buy a netflow or dpdk license for more home use. 

Sadly until recently my freebsd experience is ~2 decades old, being a linux mule for the past eras, but not dealt with ntopng just not working period on opnsense, just it being a memory hog over time.