Feature #15960
open
NTOP Port Configuration in WebUI feature request
0%
Description
Environment:
OS name: pfSense+
OS version: 24.11-RELEASE (FreeBSD 15.0-CURRENT)
Architecture: amd64
ntopng version/revision: 5.6.0_1
What happened:
When adding different ports under the advanced configuration like these:
--http-port=3000
--https-port=3001
It fails to start the service because now in the config file it has the following:
This file is automatically generated -- do not edit
--daemon=
--pid=/var/run/ntopng.pid
--data-dir=/var/db/ntopng/
--no-promisc=
--http-port=0
--https-port=0.0.0.0:3000,[::]:3000
--interface=lagg0.100
--dns-mode=0
Custom configuration options:
--http-port=3000
--https-port=3001
This means I need to remove the 2 lines it automatically generated (http-port and https-port) and manually start the service via the pfsense WebUI.
How did you reproduce it?
You just need to create a small change via the WebUI of pfsense+ in the NTOPNG settings page and then you will find yourself the need for manually having to change the ntopng.conf file and manually having to start the service from the pfsense+ WebUI
Conclusion:
A feature request to allow you to change the ports being used for the WebUI in order to avoid having the service not start because of a duplicate config line in the configuration file.
Debug Information:
N/A
Platform: Netgate 7100 1U
Updated by Denny Page about 2 months ago
Neither http-port nor https-port should not be added to the advanced configuration section. The http/https setting for ntopng is automatically controlled by the package to match the setting of pfSense itself.