Ntopng Unable to start HTTP server (IPv4) on ports 3000: Address already in use
-
Have you tried accessing ntopng by IP address?
-
Have you tried accessing ntopng by IP address?
Yes of course, IP:3000 and from the pfsense interface.. Both are timing out.
As you can see from sockstat output, ntopng is indeed using port 3000
root ntopng 9951 18 tcp4 *:3000 *:*But why would it try to start another process and issue the "port already used" error unless something else was using port 3000?
Thats when I connected my issue with orphaned packages (which includeds ntop) to this problem. Perhaps it has nothing to do with this but maybe it does.
-
Just to be sure, when you click in the address bar of the browser, it's showing an http connection rather than an https connection?
-
the link (Access ntopng) from Diagnostics > ntopng settings points to "pfsense:3000".
My pfsense firewall is accessible via https://pfsense
I tried with https, http, the actual numeral IP, the hostname (pfsense), everything is timing out.
-
And does ntopng show as running or stopped in the service status page?
-
@lpallard:
the link (Access ntopng) from Diagnostics > ntopng settings points to "pfsense:3000".
My pfsense firewall is accessible via https://pfsense
I tried with https, http, the actual numeral IP, the hostname (pfsense), everything is timing out.
I'm asking did you specifically try "http://ipaddr:3000/" not "http://pfsense".
Nothing with "https://" will work for sure.
-
@lpallard:
I tried with https, http, the actual numeral IP, the hostname (pfsense), everything is timing out.
Yes I did! Sorry if it wasnt clear ;)
IN my case it would be "http://192.168.0.1:3000/"
Edit: I tried to kill the ntopng process manually (killall ntopng) then starting the process back up and confirming it is indeed listed with sockstat (which it was) and then I tried to access it to no avail…
-
@lpallard:
Yes I did! Sorry if it wasnt clear ;)
IN my case it would be "http://192.168.0.1:3000/"
Just wanted to make sure. If it doesn't work with explicit http by ipaddr, then it isn't the hsts issue.
Have you checked the firewall log for port 3000 hits?
-
@lpallard:
Yes I did! Sorry if it wasnt clear ;)
IN my case it would be "http://192.168.0.1:3000/"
Just wanted to make sure. If it doesn't work with explicit http by ipaddr, then it isn't the hsts issue.
Have you checked the firewall log for port 3000 hits?
Damn, you hit the nail right on the head! Port 3000 was indeed being blocked by the firewall. I added a rule to allow communication from any LAN client to LAN address:3000 and now I can access ntopng!
That aside, it still doesnt explain the "[HTTPserver.cpp:503] ERROR: Unable to start HTTP server (IPv4) on ports 3000: Address already in use"
Is it something to worry about?
**Edit: How do you display sessions (both historical and current) with ntop 2.3? 15 minutes later, all I see are useless pie charts with "something" (x%) and "everything else" (100-x%)… In the previous ntop I could easily display the connections a specific host established as seen on this screenshot http://www.ntop.org/wp-content/uploads/2011/11/l7_sessions.png)
==> They're making this stuff too complicated for nothing...**
-
@lpallard:
That aside, it still doesnt explain the "[HTTPserver.cpp:503] ERROR: Unable to start HTTP server (IPv4) on ports 3000: Address already in use"
Is it something to worry about?
I recall seeing this issue early on with my dev system when I was working on a package upgrade. I don't see it any more, but I'm using a slightly newer version of the package which supports https. It's unclear if the disappearance of the error is related or not.
Regardless, I wouldn't stress over it as long as your access via port 3000 is working.
-
OK then I will not stress too much with this.
I took a good note of creating a FW rule in the future should I reinstall everything from scratch….
Thanks a lot!
