Apache server ends up “blacklinsting” browsers

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
0
down vote

favorite












I've installed Zurmo CRM on Ubuntu 16.04 server on a server (OVH Virtual Private Server -KVM OpenStack, 1 vCore(s), 2,4 GHz, 4 Go RAM, 20 Go SSD - way above the app requirements).
It works perfectly fine for a couple of uses, but after a while some screens, maybe heaver than others, freeze during 120s then say "Sorry".
When I restart apache(2) or wait those 2 minutes, the CRM is back online but those screens will have the same behavior.



Here is the funny part: when I try with another browser, I can access the faulty screens during a fiew minutes/uses until the app freez again ... and will no longer be available on the newly tested brother.
It's like if after a couple of uses, the browsers were "blacklisted" by the server, for those screens ...
It was the same for Chrome then Edge then Firefox then Chrome "Incognito" ... now none of them can access those screens...



I've been working on the php.ini but it showed no effect.
Any idea?
Thanks for your help.










share|improve this question

























    up vote
    0
    down vote

    favorite












    I've installed Zurmo CRM on Ubuntu 16.04 server on a server (OVH Virtual Private Server -KVM OpenStack, 1 vCore(s), 2,4 GHz, 4 Go RAM, 20 Go SSD - way above the app requirements).
    It works perfectly fine for a couple of uses, but after a while some screens, maybe heaver than others, freeze during 120s then say "Sorry".
    When I restart apache(2) or wait those 2 minutes, the CRM is back online but those screens will have the same behavior.



    Here is the funny part: when I try with another browser, I can access the faulty screens during a fiew minutes/uses until the app freez again ... and will no longer be available on the newly tested brother.
    It's like if after a couple of uses, the browsers were "blacklisted" by the server, for those screens ...
    It was the same for Chrome then Edge then Firefox then Chrome "Incognito" ... now none of them can access those screens...



    I've been working on the php.ini but it showed no effect.
    Any idea?
    Thanks for your help.










    share|improve this question























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I've installed Zurmo CRM on Ubuntu 16.04 server on a server (OVH Virtual Private Server -KVM OpenStack, 1 vCore(s), 2,4 GHz, 4 Go RAM, 20 Go SSD - way above the app requirements).
      It works perfectly fine for a couple of uses, but after a while some screens, maybe heaver than others, freeze during 120s then say "Sorry".
      When I restart apache(2) or wait those 2 minutes, the CRM is back online but those screens will have the same behavior.



      Here is the funny part: when I try with another browser, I can access the faulty screens during a fiew minutes/uses until the app freez again ... and will no longer be available on the newly tested brother.
      It's like if after a couple of uses, the browsers were "blacklisted" by the server, for those screens ...
      It was the same for Chrome then Edge then Firefox then Chrome "Incognito" ... now none of them can access those screens...



      I've been working on the php.ini but it showed no effect.
      Any idea?
      Thanks for your help.










      share|improve this question













      I've installed Zurmo CRM on Ubuntu 16.04 server on a server (OVH Virtual Private Server -KVM OpenStack, 1 vCore(s), 2,4 GHz, 4 Go RAM, 20 Go SSD - way above the app requirements).
      It works perfectly fine for a couple of uses, but after a while some screens, maybe heaver than others, freeze during 120s then say "Sorry".
      When I restart apache(2) or wait those 2 minutes, the CRM is back online but those screens will have the same behavior.



      Here is the funny part: when I try with another browser, I can access the faulty screens during a fiew minutes/uses until the app freez again ... and will no longer be available on the newly tested brother.
      It's like if after a couple of uses, the browsers were "blacklisted" by the server, for those screens ...
      It was the same for Chrome then Edge then Firefox then Chrome "Incognito" ... now none of them can access those screens...



      I've been working on the php.ini but it showed no effect.
      Any idea?
      Thanks for your help.







      server apache2






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Feb 20 at 15:18









      stettcher

      11




      11




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          try to find system logs and check if some info about the errors.



          The "faulty screens" are consulting some Database, can be the workload to heavy and provoke a timeout?






          share|improve this answer




















            Your Answer







            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "89"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            convertImagesToLinks: true,
            noModals: false,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













             

            draft saved


            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1008075%2fapache-server-ends-up-blacklinsting-browsers%23new-answer', 'question_page');

            );

            Post as a guest






























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            try to find system logs and check if some info about the errors.



            The "faulty screens" are consulting some Database, can be the workload to heavy and provoke a timeout?






            share|improve this answer
























              up vote
              0
              down vote













              try to find system logs and check if some info about the errors.



              The "faulty screens" are consulting some Database, can be the workload to heavy and provoke a timeout?






              share|improve this answer






















                up vote
                0
                down vote










                up vote
                0
                down vote









                try to find system logs and check if some info about the errors.



                The "faulty screens" are consulting some Database, can be the workload to heavy and provoke a timeout?






                share|improve this answer












                try to find system logs and check if some info about the errors.



                The "faulty screens" are consulting some Database, can be the workload to heavy and provoke a timeout?







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Feb 20 at 15:46









                Oscar Soriano

                14




                14



























                     

                    draft saved


                    draft discarded















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1008075%2fapache-server-ends-up-blacklinsting-browsers%23new-answer', 'question_page');

                    );

                    Post as a guest













































































                    Popular posts from this blog

                    pylint3 and pip3 broken

                    Missing snmpget and snmpwalk

                    How to enroll fingerprints to Ubuntu 17.10 with VFS491