![]() in HTTPserver.cpp there is the part of auth check and then relocates the user back to log-in page.I really gotta go, spent 12 hours already but maybe this could be a hint or not that HTTPserver.cpp got to be fixed as the 'product'. I maybe could achieve it if I try more hours but I think it's worth it for me to end up here.Ībout flushing DB, the manual needs to be updated, redis updated commands.Īnyways, I flushed and nuked the both DB, and then reinstalled it. It was one of the very rare experiences that I could not troubleshoot. ![]() I really hope not my server got compromised. it's not only me and I only use 2 awesome strength passwords in my whole life. However, in redis some funky md5 was there, mismatch the file admin md5. If I grep the password from the db file, i get the right md5 Hopefully this helps anyone else that experiences this. something in my cookie data was preventing my login. i cleared 5 cookies from the ntopng page and THAT fixed it. I made sure i had all extensions off and still no dice. The solution below should be the straight-forward solution, right? and the result is not worked, i also discovered what was probably my issue all along, in chrome if i tried to login, once i hit login, the login page would reload, never letting me in. I also tried on that stressful OS Windows 10, using legacy internet explorer that I never use. Successfully connected to redis chrome - delete full cache and data even passwords - incognito mode, no addons - admin / admin - no error message, it just resets it. Redis-cli -s /var/run/redis/redis.sock DEL it upgraded to premium 10 minutes demo, however, i can't even log in.Īlso, test if reboot really brakes the login as well since I can't go back to the state when it worked. I gave up it just worked at the fresh install then after 3 days one yum update took me 10 hours of no sleep on troubleshooting. Setting a redis password is also a good idea, please check out this for more security advices: īoth bound to 127.0.0.1 with raw mangle and filter on. In general you should never expose services to open ports into the internet. Can you report the exact command sequence you are using to reset the password? From the dashboard, you can assign to each user individually the network interfaces or networks they are permitted to evaluate.The password reset method should work as long as you can run commands in your system. Click on the gear (Settings) icon top right on the dashboard ( Figure 1) to enter user management and create a new user. Because the admin user cannot be disabled, you will want to set a very secure password for this user and define a second user with admin rights for administration work later on. Username and password, you will be prompted to set a new password. If this cannot be avoided, you can move the ntopng HTTP server to another port above 1024 (e.g., use -https-port=4443 and then log in with the URL ). To avoid conflicts with other web servers, you will want to make sure first that another web server is not already using TCP port 443 on the ntop server. For internal use, self-signed certificates are certainly justifiable: Disable the unencrypted connection and enable the SSL-protected web server by adding the following lines to the /etc/ntopng/nf file, -http-port=0Īnd restarting ntopng by typing: sudo systemctl restart ntopng A step-by-step guide can be found in a blog post online. The free Let's Encrypt CA is a good way to do this. If you prefer to run ntopng under an official domain name, you can secure the SSL/TLS connection with an official certificate. Unfortunately, the web server launches with an unencrypted connection this setup is not a good idea for security reasons because ntop is delivered with self-signed SSL certificates that throw warning messages in the browser. Ntopng launches automatically after installation you can access the web interface directly over.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |