Home › Forums › Support Forum › [SOLVED] Failing or Timing-out? Automatically Fix SELECTED Files Now
Tagged: Automatically Fix SELECTED files, failure, repair
This topic contains 5 replies, has 2 voices, and was last updated by Prodos Marinakis 8 years, 9 months ago.
-
AuthorPosts
-
February 4, 2016 at 5:26 pm #1382
Greetings.
I’m having a problem fixing a couple of my infected websites.
After completing “Run Complete Scan“, I attempt to run “Automatically Fix SELECTED Files Now!“
This pop-up begins …. but never ends ….
http://fismotron.education/wp-content/uploads/2015/05/automatically-fix-selected-files-01.jpg
After 7 days and 7 nights have passed (or so it seems) I decide to click “If this is taking too long, click here” and get this:
http://fismotron.education/wp-content/uploads/2015/05/automatically-fix-selected-files-02.jpg
See the sad little rectangle? That’s what I feel like.
Emotions aside …
Any thoughts on what might be causing this?
Is there something I can do about it?Thanks for any assistance.
Best Wishes,
PRODOS
Melbourne, AustraliaFebruary 4, 2016 at 5:44 pm #1385Unfortunately I cannot tell from your screenshots how many Known Threats you have there but I suspect it may be more than your server can handle fixing in one click. I also cannot tell how long it took for the scan to finish producing those results but my first suggestion would be to start the scan again and this time employ the fix-as-you-go method which means you click on the Automatic Fix button as soon as there is anything to fix but you let it keep scanning at the same time. That way it fixes things in smaller batches and by the time the scan is finished the fixing would be not far behind.
P.S. As a point of reference, it shouldn’t take more than 60 seconds for that popup window/frame to produce it results (if it’s going to at all).
February 5, 2016 at 2:20 am #1386Dear Eli,
Thanks for your thoughts and advice.
I’m having better success with cleaning up my sites now that I’ve connected to my ADSL with the ethernet cord.
Still getting the occasional timing out, but eventually it works.
Best Wishes,
PRODOS
February 5, 2016 at 4:55 am #1388Dear Eli,
I was having a time-out problem with one of my infected sites. It had over 200 infected files.
You suggested:
… employ the fix-as-you-go method which means you click on the Automatic Fix button as soon as there is anything to fix but you let it keep scanning at the same time.
I tried that and it worked for a while.
Then a big batch of bad files came up and the Automatic Fix wasn’t able to handle it.
I restarted the scan and let it complete.
Then unchecked all the red-coloured bad files.
Then checked 10 of them at a time and ran the fixer on those. This worked.
A couple of times I tried a larger batch. At about 16 at a time the fixer started to time-out (i.e. it just kept churning away but never completing).
Currently my ADSL internet seems to be running slow. And using the modem’s WiFi (when I take the computer into the house) is even slower.
Perhaps when (hopefully) ADSL performance improves there won’t be all these time-out issues.
Even so, I think it might be helpful to have a way of unchecking all the infected files and to have a way of checking these files in batches. Maybe.
Best Wishes,
PRODOS
Melbourne, AustraliaFebruary 5, 2016 at 7:39 am #1389Good idea, un-checking and then check only a few at a time is another good way to split up the batch site, but I realize that would be easier with options for “Check All” and “Uncheck All”.
Having a stable internet connection is important when you are running long scans because the Complete Scan relies on JavaScript call from your browser to keep the scan going. This is one of the reasons it been so hard for me to create the scheduled scan feature that everyone wants. However, I don’t think your internet connection speed has anything to do with the timeout issue you are having when you try to fix larger batches. That kind of problem really relies more on the speed of the server then the client. Last year I was using a Satellite Internet provider, which was way slower than any DSL connect I had ever used, and those kind of timeout issues completely depended on what server I was running my plugin on. Some server have very little physical memory and are overburdened with site that cause them to run too many processes too slowly. Also there could be settings in your php.ini like memory_limit or max_execution_time which are restricting the abilities of the php code running on your site.
February 8, 2016 at 5:29 pm #1401Greetings Eli,
Thought I’d report that the automatic removal tool seems to be working well again.
I think you’re right, that the problem was with my server … which has been massively infected — to the point where it was slowing down.
It’s a nightmare, really.
My server provider (ServInt) has recommended I set up separate cPanels for each website in order to avoid sites infecting each other from within the server.
A massive hassle.
But some sites get re-infected after being cleaned, so I suppose I’m going to have to bite the bullet and follow their suggestion.
Best Wishes,
PRODOS
-
AuthorPosts
You must be logged in to reply to this topic.