Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Behind the Scenes
  3. Qt.io webservices
  4. Connection to Forum always lost on FireFox?
Forum Updated to NodeBB v4.3 + New Features

Connection to Forum always lost on FireFox?

Scheduled Pinned Locked Moved Unsolved Qt.io webservices
12 Posts 8 Posters 3.1k Views 3 Watching
  • 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.
  • D Offline
    D Offline
    davecotter
    wrote on last edited by
    #1

    FireFox won't stay connected. When i view the forums, i get the spinny thing at the top of the window:

    0_1535951759301_Screen Shot 2018-09-02 at 10.09.39 PM.png
    and this message at the bottom right:

    0_1535951773145_Screen Shot 2018-09-02 at 10.09.27 PM.png

    pretty consistently. it goes away sometimes, after a while. but it happens EVERY time. Chrome seems to work, at least the ONE time i tried it (now)

    JonBJ 1 Reply Last reply
    1
    • JohanSoloJ Offline
      JohanSoloJ Offline
      JohanSolo
      wrote on last edited by
      #2

      I'm only using Firefox and don't have the problem you're describing. Try in a private windows, if working this could indicate a cookie problem or incompatibility with an add-on.

      `They did not know it was impossible, so they did it.'
      -- Mark Twain

      D 1 Reply Last reply
      0
      • aha_1980A Offline
        aha_1980A Offline
        aha_1980
        Lifetime Qt Champion
        wrote on last edited by
        #3

        @davecotter I have this too, and I remember a thread one or two weeks ago from @VRonin who had the same problem. I seems to be a forum software bug.

        Regards

        Qt has to stay free or it will die.

        1 Reply Last reply
        0
        • VRoninV Offline
          VRoninV Offline
          VRonin
          wrote on last edited by
          #4

          Can confirm it happens to me too a lot. Looks like this bug but the workaround suggested doesn't work for me

          "La mort n'est rien, mais vivre vaincu et sans gloire, c'est mourir tous les jours"
          ~Napoleon Bonaparte

          On a crusade to banish setIndexWidget() from the holy land of Qt

          1 Reply Last reply
          1
          • D davecotter

            FireFox won't stay connected. When i view the forums, i get the spinny thing at the top of the window:

            0_1535951759301_Screen Shot 2018-09-02 at 10.09.39 PM.png
            and this message at the bottom right:

            0_1535951773145_Screen Shot 2018-09-02 at 10.09.27 PM.png

            pretty consistently. it goes away sometimes, after a while. but it happens EVERY time. Chrome seems to work, at least the ONE time i tried it (now)

            JonBJ Offline
            JonBJ Offline
            JonB
            wrote on last edited by
            #5

            @davecotter
            I use FF under Linux and it happens to me all the time. I thought it was me! :)

            1 Reply Last reply
            0
            • JohanSoloJ JohanSolo

              I'm only using Firefox and don't have the problem you're describing. Try in a private windows, if working this could indicate a cookie problem or incompatibility with an add-on.

              D Offline
              D Offline
              davecotter
              wrote on last edited by
              #6

              @JohanSolo using a private window did not help, same problem

              1 Reply Last reply
              0
              • S Offline
                S Offline
                StringTheory
                wrote on last edited by StringTheory
                #7

                I get this same error with Chrome browser. I'm not sure if it's browser-dependent or something more subtle, but I just had to use a different machine that has an ancient version of Google's Canary (experimental) browser to post the last couple messages to this forum.

                I've been seeing the error under Chrome for months, but today, it was impossible to post anything. I could log in. I could read forum messages, but pressing the 'new topic' button did nothing.

                Both machines are running Windows. I'll check the Linux machines later, but I'm sure I've seen similar in the past.

                You'd think it would be relatively easy to trace that error message back to its source. Perhaps it's some kind of watchdog timeout glitch.

                1 Reply Last reply
                0
                • VRoninV Offline
                  VRoninV Offline
                  VRonin
                  wrote on last edited by
                  #8

                  Ping @ollipuu if you know more how we could solve/get around this problem (cc @AndyS)

                  "La mort n'est rien, mais vivre vaincu et sans gloire, c'est mourir tous les jours"
                  ~Napoleon Bonaparte

                  On a crusade to banish setIndexWidget() from the holy land of Qt

                  1 Reply Last reply
                  0
                  • AndySA Offline
                    AndySA Offline
                    AndyS
                    Moderators
                    wrote on last edited by
                    #9

                    Assuming that it is in fact the same problem as reported on NodeBB then it seems that we are stuck in this respect if the workaround is not working. They are waiting on a fix in a package they depend on too so I don't know much more about how it can be worked around. If more users are ending up having more problems however with the latest version of Chrome/Firefox then we'll have to see if we can somehow solve it more directly.

                    Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                    1 Reply Last reply
                    2
                    • ollipuuO Offline
                      ollipuuO Offline
                      ollipuu
                      wrote on last edited by
                      #10

                      I tried to reproduce the issue, but without luck. I subscribed to that NodeBB ticket just in case that socket.io bug gets fixed and then we could maybe think about updating the forum software at the same time.

                      1 Reply Last reply
                      3
                      • S Offline
                        S Offline
                        StringTheory
                        wrote on last edited by
                        #11

                        I just tried Internet Explorer on the same machine where Chrome gave the lost connection message. I figured that it would show the same, but ... surprise, no disconnect message. Weird.

                        1 Reply Last reply
                        0
                        • VRoninV Offline
                          VRoninV Offline
                          VRonin
                          wrote on last edited by VRonin
                          #12

                          I now stopped having this problem. As an important note, however, the workaround suggested in the NodeBB bug report breaks completely the bugreports.qt.io system

                          "La mort n'est rien, mais vivre vaincu et sans gloire, c'est mourir tous les jours"
                          ~Napoleon Bonaparte

                          On a crusade to banish setIndexWidget() from the holy land of Qt

                          1 Reply Last reply
                          0

                          • Login

                          • Login or register to search.
                          • First post
                            Last post
                          0
                          • Categories
                          • Recent
                          • Tags
                          • Popular
                          • Users
                          • Groups
                          • Search
                          • Get Qt Extensions
                          • Unsolved