Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Cannot Log into ntopng

    Scheduled Pinned Locked Moved Traffic Monitoring
    21 Posts 10 Posters 18.7k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • KOMK
      KOM
      last edited by

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

      1 Reply Last reply Reply Quote 0
      • R
        reggie14
        last edited by

        @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.

        1 Reply Last reply Reply Quote 0
        • cyber7C
          cyber7
          last edited by

          @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
          idiot.png_thumb

          When you pause to think, do you start again?

          2.2.4-RELEASE (amd64)
          built on Sat Jul 25 19:57:37 CDT 2015
          FreeBSD 10.1-RELEASE-p15
          and
          pfSense 2.3.2-RELEASE-p1 (amd64 full-install) on pfSense

          1 Reply Last reply Reply Quote 0
          • dennypageD
            dennypage
            last edited by

            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.

            1 Reply Last reply Reply Quote 0
            • cyber7C
              cyber7
              last edited by

              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…

              When you pause to think, do you start again?

              2.2.4-RELEASE (amd64)
              built on Sat Jul 25 19:57:37 CDT 2015
              FreeBSD 10.1-RELEASE-p15
              and
              pfSense 2.3.2-RELEASE-p1 (amd64 full-install) on pfSense

              1 Reply Last reply Reply Quote 0
              • dennypageD
                dennypage
                last edited by

                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?

                1 Reply Last reply Reply Quote 0
                • cyber7C
                  cyber7
                  last edited by

                  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
                  NTOP.png_thumb

                  When you pause to think, do you start again?

                  2.2.4-RELEASE (amd64)
                  built on Sat Jul 25 19:57:37 CDT 2015
                  FreeBSD 10.1-RELEASE-p15
                  and
                  pfSense 2.3.2-RELEASE-p1 (amd64 full-install) on pfSense

                  1 Reply Last reply Reply Quote 0
                  • KOMK
                    KOM
                    last edited by

                    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.

                    1 Reply Last reply Reply Quote 0
                    • P
                      pstuart
                      last edited by

                      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.

                      1 Reply Last reply Reply Quote 0
                      • C
                        capn_buzzcut
                        last edited by

                        Confirm this fix worked for me

                        1 Reply Last reply Reply Quote 0
                        • dennypageD
                          dennypage
                          last edited by

                          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.

                          1 Reply Last reply Reply Quote 0
                          • R
                            rkelleyrtp
                            last edited by

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

                            1 Reply Last reply Reply Quote 0
                            • cyber7C
                              cyber7
                              last edited by

                              @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!

                              When you pause to think, do you start again?

                              2.2.4-RELEASE (amd64)
                              built on Sat Jul 25 19:57:37 CDT 2015
                              FreeBSD 10.1-RELEASE-p15
                              and
                              pfSense 2.3.2-RELEASE-p1 (amd64 full-install) on pfSense

                              1 Reply Last reply Reply Quote 0
                              • First post
                                Last post
                              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.