ScalarEnt

I apear to be having a similar problem. I have tried migrating 2 sites over to my test server on Heart Internet multiple times with Duplicator 1.3.10 and they both stop after Step 1 with just a white screen with the URL https://ny-url/dup-installer/main.installer.php

dup-installer-bootlog

Last line:

Apr 10 09:13:59 No detected errors so redirecting to the main installer. Main Installer URI = https://my-url/dup-installer/main.installer.php

dup-installer-log

Last Line:

STEP-1 COMPLETE @ 09:15:52 – RUNTIME: 56.6809 sec.

I tried running an older Duplicator package (ver 1.2.52) install on another test site and that worked fine.

Is this a problem with Duplicator 1.3.10 ?

• This reply was modified 5 years, 11 months ago by ScalarEnt.

Great news about the roll back, my sites seem to be scanning correctly again now.

Hope that Heart and Wordfence can find a workable solution.

Thanks guys.

All of my sites I’ve looked at so far have max execution time set to 180 ! Seems to be set by Heart.

I just changed it back to the default (0) on one site and it now completes the scans without previous error:

[Oct 25 15:56:55:1540479415.459893:1:error] Fatal error: Maximum execution time of 30 seconds exceeded in /home/sites/businessbuilderfs.co.uk/public_html/wp-content/plugins/wordfence/lib/wordfenceScanner.php on line 367

However, it still took nearly 4 minutes

[Oct 25 16:10:44:1540480244.456991:1:info] Scan Complete. Scanned 7723 files, 15 plugins, 4 themes, 31 posts, 0 comments and 1845 URLs in 3 minutes 58 seconds.
[Oct 25 16:10:44:1540480244.455711:2:info] Wordfence used 33 MB of memory for scan. Server peak memory usage was: 112.75 MB

Response from Heart

Lately we noticed that there are so many websites with WordFence plugin hosted on our servers. According to the WordFence developers those scans are normally running for 5-15 minutes on shared hosting. Sadly, this is not acceptable for our shared hosting platform, because such processes are considered as permanent and high resource usage ones. Because of the origin of the shared hosting (to host many sites on same server) our servers were suffering from high load issues because of the run of 100’s scans a day. This all caused our shared hosting platform not to offer reliable service lately.

Please keep in mind that according to out terms and conditions, on the shared hosting platform it is allowed to use up to 5% of the resources of the whole server and running those scans is actually abusing our servers lately.

This forced us to implement some changes on the shared hosting platform to restrict the time for which those scans can run to 180 seconds (3 minutes) and even if you set php.ini file to increase the PHP max execution time values, it will be disregarded.

From what I see, the WordFence scans are taking more time in cases when the website is full of content – some files in the wp-content folder and many old post, comments etc. in the database. Because of this I can say it is a good idea to try to optimize the website and remove all old content that is not being used anymore and also to optimize the wordpress database.

If you want to see more on this I would recommend checking out wordfences docs on this here –> https://www.wordfence.com/help/scan/troubleshooting/#scan-time-limit-exceeded

They state in the URL above that limits like these are common shared hosting plans the difference with us is that we change them on the client side so you can see them, rather than limiting them on the backend and killing the processes without telling (Which is common on shared hosting). They are changes mentioned in the URL you can make to your scans to limit the resources being used which should avoid these issues. I would recommend that you disable scanning outside your wordpress install and disable “Scan images, binary, and other files as if they were executable”.

Of course another workaround will be to get a VPS, where you will be able to set the restrictions on your own, but in my opinion the suggestion to try to optimize the whole website first worth trying.

Hi wfasa,

I totally agree with what you say. Most of my sites having this problem are actually quite small but Heart’s shared servers typically are quite slow most of the time and hence scans take more than 3 minutes.

Their comment about upgrading to VPS is just not necessary and they seem to be using it as an excuse to get people to upgrade rather than them fixing their slow servers.

I will also raise this with Heart.

Thanks @cucocreative – didn’t realise that

Hi wfasa,

I have emailed the full scan log to you as requested.

If it helps, I have noticed that all my sites having this issue are on Heart Internet or 123-reg hosting. Others on 1&1 hosting seem to be OK.

Steve

Wordfence updated to new version 7.1.16 ;ast night but still getting fatal error:

[Oct 17 08:59:44:1539763184.950709:1:error] Fatal error: Maximum execution time of 30 seconds exceeded in /home/sites/charlottewooddance.co.uk/public_html/wp-content/plugins/wordfence/lib/wordfenceScanner.php on line 389

I get similar errrors on “Limited scan”

Running scan again on same site I get a differnet error:

[Oct 16 09:25:27:1539678327.644164:1:error] Fatal error: Maximum execution time of 30 seconds exceeded in /home/sites/charlottewooddance.co.uk/public_html/wp-content/plugins/wordfence/lib/wordfenceScanner.php on line 389

SAme story on a different site but different error:

[Oct 16 09:20:23:1539678023.735721:1:error] Fatal error: Maximum execution time of 30 seconds exceeded in /home/sites/charlottewooddance.co.uk/public_html/wp-includes/wp-db.php on line 2794

Thanks for clarifying guys.

Thanks, I’ll check

Sorry I forgot to mention it is on Apache server.

I have the same issue – I added the code to the htaccess file and it fixes.

Why wasn’t it added during the Firewall Optimization process ?