Closed cobrafast closed 8 years ago
when did the error start showing up? Did you update something?
That's hard for me to tell as I hadn't used ntopng in a while and several updates were done meanwhile.
so I think we should try and start with a clean install. Use apt to completely remove ntopng and make sure no ntopng process is active. Then
apt-get clean all
apt-get update
apt-get install ntopng
start ntopng and try again.
You can also try the following to reset the admin password:
Resetting admin user password
-----------------------------
1. shutdown ntopng
2. redis-cli del ntopng.user.admin.password
3. restart ntopng and now the admin password has been reset
Okay, I did all this. Nothing changed.
please, paste full ntopng log
The log file attached does not have the errors you shown in the first post. It looks ok.
Sorry, verbose isn't activated by default and I didn't check.
Here is a new log with verbose option activated: http://pastebin.com/SRUCbHXi
Line 698 is where my error message is at.
no username is send to ntopng. Indeed, there is nothing after the slash in the error shown.
11/Apr/2016 17:49:51 [HTTPserver.cpp:212] [HTTP] Session 724e3820ca5f317906df81bad926f771/ is expired or empty user
This means that an empty string has been submitted as the username. This line confirms what I'm saying: https://github.com/ntop/ntopng/blob/dev/src/HTTPserver.cpp#L218
Please, update to the latest package and report the exact procedure you do to login. If you log in via the standard login page, use the browser inspector to see if the HTTP request with user and password is correctly send out.
Support given. No feedback or information provided in 6 days. Closing for inactivity. If you are still experiencing the issue please open another issue with the requested information.
Dude your software doesn't work. Default credentials don't work. I've seen this happen on PFsense, as well as your windows build. Should be simple to fix.
@Elefontman saying that won't help, if you really need help remember to post useful information such as build, os and architecture, logs, errors, and, more in general, how to reproduce.
Useful information: All of your builds don't work with their default pwd, whether it's Windows or Linux, and I've seen it on Pfsense as well. Pathetic.
@simonemainardi here's an interesting data point, may help you track this one down: For some reason, if i tunnel to localhost (so my connection looks like it's coming from localhost) I can log in. If i try the machine on port 3000 directly, i get the webpage, but i can't log in. Is there any debug logs or something I can provide you with?
@lordmortis what operating system are you using? What version of ntopng?
Ubuntu 16.04 64bit. here is the output from DPKG
ii apt-ntop-stable 2.4-514 all ntop stable apt package repository
ii ntopng 2.4.170202-2319 amd64 Web-based traffic monitoring.
ii ntopng-data 2.4.170202 all Data files (geoip) for ntopng.
ii pfring 6.4.1-1118 amd64 PF_RING (http://www.ntop.org/pf_ring/) [6.4.1-stable:a53472d382180014602836f8310558f046e890a8 (Fri Jan 27 19:28:33 2017 +0100)]
I've installed it via wget http://apt-stable.ntop.org/16.04/all/apt-ntop-stable.deb
, then installing that DPKG and apt-get'ing the above packages.
Interestingly enough I just tried to login again (this time not over the VPN) and it worked. I will try via VPN later on tonight and update with how I went.
Thank you. The more information we have, the easier it will be for us to troubleshoot the problem.
So - I'm not sure what changed between the first night i tried things and the next day but it started working (sorry for not replying before now). If you want any more debugging info i can try and give it to you, but it seems like waiting a few hours fixed it?
I could reproduce the issue. I did a clean install through apt-get on ubuntu 16.04. I tried to login with my Safari (macOS 10.12.3 & 10.12.4(beta)) -> loopback to login page After reading some of these answers I changed to Chrome> login worked
@Dafubar did you use an hostname? Or just the loopback IP address?
I was unable to login using admin/admin at localhost:3000. But when I switched from localhost to my non-loopback IP address it worked, i.e. 192.168.0.123:3000
Fresh install, Centos 7. Using the hostname (http://ntop.mylocal.com:3000/) does not work. Using the IP (http://192.168.1.8:3000) does.
I have having similar issues. It's quite odd - sometimes it will let me login and other times it won't - using the same browser, system etc. Clearing cookies etc. does not seem to help and examining the post requests confirms the username and password are being sent.
@peter-manton can you describe the exact ntopng and browser versions?
@simonemainardi
Client machine:
uname -r 4.11.3-200.fc25.x86_64 chromium-browser --version Chromium 58.0.3029.110 Fedora Project
Server:
ntopng --version v.3.0.170623 [Enterprise/Professional Edition] GIT rev: 3.0-stable:878a45815810492103895da8a906c3c3c11892fb:20170623 Pro rev: r1101 System Id:
Built on: CentOS Linux release 7.3.1611 (Core)
do you use a symbolic name in the browser url, or just the ip address? Using centos7 I was experiencing some issues when using a name defined in (/etc/hosts)
@simonemainardi I'm currently using the IP address to access it. I'm going to spend some time tomorrow to see if I can dig a little deeper into this.
@peter-manton just experienced the same issue. This is a very old chromium bug, still not fixed https://bugs.chromium.org/p/chromium/issues/detail?id=150066 which prevents chromium from setting cookies on HTTP redirect (302).
A note: with HTTPS it seems to work Update: opening the developer console -> Application -> Cookies -> http:://127.0.0.1:3000 -> Clear All seems to reset chromium and HTTP login works again
https://github.com/ntop/ntopng/blob/dev/doc/README.md shows the current procedure for resetting the admin password.
Please also check out https://github.com/ntop/ntopng/commit/07702712187347ef448a14647d051c223755b4cd
Attempting to login with valid credentials fails with
the behaviour or error message does not change after a
redis-cli flushall
. Even the shown session ID remains identical.Version: 2.2+dfsg1-2 (debian/sid) Kernel: 4.3.3-7 x86_64