Cannot Log into ntopng

rpenalis

I tried Edge and it works! Very weird problem. Thank you very much for all your assistance.

dennypage

Version of pfSense? Version of ntopng package? Http or https?

grandrivers

i see issues with chrome not loginig in

2.3.3-DEVELOPMENT (amd64)
built on Wed Oct 05 02:17:09 CDT 2016
FreeBSD 10.3-RELEASE-p9

ntopng 0.8.4_4

chrome Version 53.0.2785.143 (64-bit)

macos 10.12

maybe bump to latest from quarterly ports branch 2016q4 see if it helps

KOM

Or just apply the system patch that JimP has listed at least a dozen times in various "browser don't work" threads.

reggie14

@KOM:

Or just apply the system patch that JimP has listed at least a dozen times in various "browser don't work" threads.

What are you referring to? I looked at his recent post history and didn't see anything like this.

cyber7

@reggie14:

@KOM:

Or just apply the system patch that JimP has listed at least a dozen times in various "browser don't work" threads.

What are you referring to? I looked at his recent post history and didn't see anything like this.

Thankx for nothing:

idiot.png_thumb

dennypage

A better search term is "chrome bug", but you need to execute your search from the base of the forum instead of within the traffic monitoring sub forum. If you execute a search within a sub forum, your search is restricted to that sub forum.

cyber7

OK, had a look at the patch and it does not work on 2.3.2-p1

I have an unpatched 2.2.4 system and did the install there. Guess what, NOT A CHROME BUG!!! The LOGIN works on 2.2.4, pointing to a pfSense problme, not a chrome problem…

dennypage

2.2 and 2.3 are quite different, so I wouldn't view this as an indication one way or another. It's also possible that you are experiencing a completely different problem to what others are discussing here.

Best to return to basics. Can you describe what you are seeing with 2.3.2?

cyber7

I see the problem does not occur on Google Chrome 52.0.2743.116m (64-bit), so it seems it is only in the newer release of Chrome…

I am running: 53.0.2785.143 m (64-bit)

The problem I see is I get to type in the user/pass, but then both boxes turns RED and the Login box is grayed-out.

NTOP.png_thumb

KOM

Thankx for nothing:

idiot.png (48.21 kB, 783x392 - viewed 3 times.)

Seriously? Forgive me for trying to help people for free in my spare time. I'm such an asshole.

so it seems it is only in the newer release of Chrome…

That can't be right because you just finished saying it wasn't a Chrome bug in capital letters and everything.

pstuart

Found the solution to chrome issues.

Login.lua has an error in it.

Edit /usr/local/share/ntopng/scripts/lua/login.lua

Remove the escape left of the "=" in the pattern so it matches as below:

Hope that helps.

capn_buzzcut

Confirm this fix worked for me

dennypage

Good find. That looks to be the same Chrome regex parsing bug seen elsewhere. While unnecessary, there isn't anything actually wrong with the back-slash prior to the equal sign.

/usr/local/share/ntopng/scripts/lua/login.lua is part of ntopng. A bug report could be filed upstream with ntopng, but I'm not sure they would accept it. I expect that the Chrome folk will fix it faster than anyone.

rkelleyrtp

Great fix! I ran into the same problem yesterday. Confirmed your fix worked for me as well after making the change.

cyber7

@pstuart:

Found the solution to chrome issues.

Login.lua has an error in it.

Edit /usr/local/share/ntopng/scripts/lua/login.lua

Remove the escape left of the "=" in the pattern so it matches as below:

Hope that helps.

Thank you Dear Sir
You, in my books, are not an idiot! Your answer is not only precise, but 100% spot-on.

Confirmed it works for me!