Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Impossible to login on Chrome #706

Closed
ThomasdOtreppe opened this Issue Aug 22, 2016 · 16 comments

Comments

Projects
None yet
7 participants
@ThomasdOtreppe
Copy link

ThomasdOtreppe commented Aug 22, 2016

Using Chrome Version 54.0.2836.0 canary (64-bit) on Windows 7 64 bit, it doesn't let me login.

ntopng version: ntopng Community v.2.4.160818 from ntopng repos (--community has been appended to /etc/ntopng/ntopng.conf

I haven't changed the credentials, base Ubuntu 16.04 install and ntop-ng only.

It lets me type the login no problem but when I type the password, it enable login button after the first character then disable it when typing the second character of the password and leaves it disabled which is preventing logging in. Works fine on Firefox 48.0.1 on the same OS.

@simonemainardi

This comment has been minimized.

Copy link
Member

simonemainardi commented Aug 25, 2016

Hi, I can successfully login using Version 54.0.2839.2 canary (64-bit). Please, try with the new build that will be released tomorrow as it includes the following fix that very likely is related: #700

@simonemainardi

This comment has been minimized.

Copy link
Member

simonemainardi commented Aug 29, 2016

fix and solution given. closing for inactivity.

@ThomasdOtreppe

This comment has been minimized.

Copy link
Author

ThomasdOtreppe commented Aug 29, 2016

Tested and just did a fresh install a few minutes ago and got v2.4.160818-1561. Still doesn't work.

@ThomasdOtreppe

This comment has been minimized.

Copy link
Author

ThomasdOtreppe commented Aug 29, 2016

Is there any way I can help debug the issue?

@simonemainardi

This comment has been minimized.

Copy link
Member

simonemainardi commented Aug 29, 2016

version v2.4.160818-1561 doesn't include the fix. Please use a more recent version.

@ThomasdOtreppe

This comment has been minimized.

Copy link
Author

ThomasdOtreppe commented Aug 29, 2016

That's the latest version available in packages.

@simonemainardi

This comment has been minimized.

Copy link
Member

simonemainardi commented Aug 29, 2016

look for DEV packages, not sable

@ThomasdOtreppe

This comment has been minimized.

Copy link
Author

ThomasdOtreppe commented Aug 29, 2016

Works fine with dev.

@HontoNoRoger

This comment has been minimized.

Copy link

HontoNoRoger commented Dec 30, 2016

Just tried the newest version on Ubuntu 16.04 stable repo, where it's not working.
When will a stable version with Chrome support be released to address this issue?
Thanks.

@robertdolca

This comment has been minimized.

Copy link

robertdolca commented Dec 30, 2016

I was able to reproduce it too

@xyGZen

This comment has been minimized.

Copy link

xyGZen commented Apr 15, 2017

I am also able to reproduce this issue using v.2.4.170215 on CentOS 7.3.1611

@simonemainardi

This comment has been minimized.

Copy link
Member

simonemainardi commented Apr 16, 2017

@xyGZen issue is fixed in the dev packages and will be included in the next forthcoming release

@mjhdcode

This comment has been minimized.

Copy link

mjhdcode commented Nov 30, 2018

Still happening for me on 3.6.181106 with CentOS 7.5....
Login works first time, then won't login - only on Chrome - Firefox works as expected
Thought I had lost my damn mind

@emanuele-f

This comment has been minimized.

Copy link
Contributor

emanuele-f commented Nov 30, 2018

Please update to the latest version and retry. Please also ensure that you have no blocking browser plugins installed

@mjhdcode

This comment has been minimized.

Copy link

mjhdcode commented Nov 30, 2018

I don't have any plugins, and this bug seems pretty persistent (I'm well past the dev branch version suggested in other places), I think if you want this feature to work, a more in depth response to it's existence will be needed, luckily I'm monitoring isolated local network traffic, so I don't mind having no login - I just wanted you to know this issue is still lurking and has been since at least 2014. I have seen this question asked in 2014, and re-asked in 2016, 2017 and early 2018 with various versions cited. I think this bug needs to be upgraded to snark status and hunted thusly...

@mjhdcode

This comment has been minimized.

Copy link

mjhdcode commented Nov 30, 2018

Awesome toolkit though - kudos

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.