WanderingOn

I was able to identify the database that is in use using the wp-config.php file as you suggested, thank you.

I can also see also a $table_prefix variable has been set.

I notice that in the database, there seem to be two versions of each table. One with the same prefix as is listed in the wp-config.php file and another set of (what seems to be) the same tables prefixed by a bunch of letters/numbers.

Is this typical?
Should I delete the second set of tables that are prefixed by the letters/numbers?

I am assuming this would leave the active tables only? Could this potentially improve performance/speed?

Thanks again for your help with this. I am not very familiar with databases so just want to be sure I am not going to make any major errors.

Thanks Steven. Much appreciated.

• This reply was modified 4 years, 4 months ago by WanderingOn.

Hi @sterndata

There are also two instances of index.php; index.php and index1.php – can index1.ph also safely be deleted?

Thanks

Hi Steven,

Thanks for the quick reply. I will download them now and delete all except for the wp-config.php file.

Thanks for your help.

Hi @wfadam

I have contacted the hosting company now. I will let you know what they say.

Thanks,
Brian

Tanks for the quick reply @wfadam

I contacted my hosting company recently about the MySQL errors identified in the diagnostics report. They replied to say that “None of those items listed are issues to be concerned about.” They also said that “The site is loading very quickly for me and a curl test shows:

~$ time curl -s https://wanderingon.com
real 0m0.507s
user 0m0.040s
sys 0m0.000s

That shows a load time of 0.5 seconds”

I am on a shared hosting plan. Can I reinstall the cURL myself or will the hosting company have to do it? What reason can I provide them with to highlight why this needs to be completed?

Thanks

Hi @wfadam

Yes, I am using Cloudflare CDN.

I have sent a diagnostic report using the “Send Report by Email” feature now.

If there’s anything else that I can do, please let me know.

Thanks,
Brian

Hi @wfadam

I followed your instructions and below are the last few lines of the log.

[Oct 24 18:25:45] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/assets/js/navigation.js (Mem:44.0M)
[Oct 24 18:25:45] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/assets/js/skip-link-focus-fix.js (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/comments.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/footer.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/front-page.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/functions.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/header.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/inc/back-compat.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/inc/color-patterns.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/inc/custom-header.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/inc/customizer.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/inc/icon-functions.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/inc/template-functions.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/inc/template-tags.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/index.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/page.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/search.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/searchform.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/sidebar.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/single.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/template-parts/footer/footer-widgets.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/template-parts/footer/site-info.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/template-parts/header/header-image.php (Mem:44.0M)
[Oct 24 18:25:47] Calling fork() from wordfenceHash with maxExecTime: 20
[Oct 24 18:25:47] Entered fork()
[Oct 24 18:25:48] Calling startScan(true)
[Oct 24 18:25:48] Got value from wf config maxExecutionTime: 20
[Oct 24 18:25:48] getMaxExecutionTime() returning config value: 20
[Oct 24 18:26:06] Test result of scan start URL fetch: WP_Error::__set_state(array( ‘errors’ => array ( ‘http_request_failed’ => array ( 0 => ‘cURL error 28: Operation timed out after 18001 milliseconds with 0 bytes received’, ), ), ‘error_data’ => array ( ), ))
[Oct 24 18:26:06] Starting cron via proxy at URL https://noc1.wordfence.com/scanp/wanderingon.com/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=1&scanMode=custom&cronKey=bb7dc4f3ff826edf9800cf553fa65b1c&k=0ea4bddc8c0ebdb959d92300f0217cf36015a6e9123009839227487116b6f87a74248c9d11d123ff2c8cdbd56e6d4a2a7bdca840ba9af4ccbfa0e433158e74aecbfcaa66ef069ece9ea144c7ba4417b7&ssl=1&signature=80c4bebbbe3e8d2efcfed78c021ecda70c440f560d80435c394207d82068ffb7
[Oct 24 18:26:07] Scan process ended after forking.

If you need anything else, please let me know.

Thanks,
Brian

Hi @wfadam ,

Thanks for the quick reply and for explaining the cause of this error.

Is there anything I can do to ensure that this error does not show in the Site Health check?

Thanks

Hi Mark,

Thank you for the quick reply.

I have enabled the 301 .htaccess redirect option now and everything seems to be working fine.

Thanks for your help.

Hi Tim @wfsupport ,

Thanks for the quick reply.

I am not sure if we have whitelisted our server IP address in Cloudflare. Can you please send instructions as to how I can do this? I have searched online but cannot find an answer as to how to do this.

Thanks,
Brian

Hi Tim @wfsupport ,

Thanks for your reply. We have sent your response to Ezoic now and we will let you know if they have any answers.

We are still awaiting a reply from Cloudflare support but we will update you as soon as we have an update.

In the meantime, we are still unable to complete a scan using Wordfence. We are still seeing the same error: “Scan Failed. The scan has failed to start. This is often because the site either cannot make outbound requests or is blocked from connecting to itself.” Is there anything that we can do to fix this?

Thanks,
Brian

Hi Tim @wfsupport ,

We had the following reply from Ezoic when we raised the issue for the site speed with them and the issue of the”website not connecting back to itself:

MySQL Errors & WordFence:
So this error is happening because wordfence is trying to connect to the IP for your domain which is currently showing as one of Ezoic’s IPs as we use a CDN service to speed up your websites offering. These Ezoic IPs are not hosted on a MySQL server which is causing the errors that we are seeing.

What you’ll need to do is tell wordfence to connect directly to your origin IP address instead. There might be a setting for this. Or, explain to them that you are now using a CDN service which changes the way they will see your site. Here is some documentation on how it works – Ezoic CDN

Otherwise, you could simply disable wordfence from the site altogether. What’s important to understand is that these errors aren’t actually real, they are being picked up by wordfence because they don’t realise you’ve started using a CDN.

They seem to maintain that the issue is with Wordfence. Can you please clarify?

Thanks,
Brian

Hi Tim @wfsupport ,

Just to keep you in the loop, we have heard back from WP Rocket now with the following:

Our optimizations seem to be applied, and our caching is stored properly.

Unfortunately, there is nothing that can be done in our end that will help improve performance-bottlenecks happening outside of our control.

We, and any performance plugin for that matter, have no control over what’s happening on Ezoic CDN, as well as the advertiser’s origin servers.

We hope the above information is useful. We are waiting to hear back from Cloudflare support but will update you as soon as we have a reply from them.

Thanks,
Brian

Hi Tim @wfsupport ,

Thanks for getting back to us.?

We have contacted both Cloudflare and WP Rocket support now also. Hopefully, they can provide some additional information and we can get this resolved soon.?

We will keep you updated as things progress.

Thanks,
Brian