rubiconcsl

Hi. The reason it is not activated, is because I ended up restoring the site, back about a week. I couldn’t get things to work otherwise. So, I’m back as I was before I installed Super Page Cache. I’m probably going to leave it as it was and not now install Super Page Cache. Not ideal and not as quick a site as I’d like, but it at least all now loads 😕

Whilst awaiting a reply, I took the engineers’ approach of “switch it off and back on again” i.e. deactivated the plugin and re-activated it. The error has gone away, even though I still can’t see the file it was looking for anywhere (well, not obviously related to CleanTalk anyway).

[public_html]$ pwd
/xxxx/xxx/public_html
[public_html]$ find . -name “cacert.pem” -type f 2>/dev/null
./wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/cacert.pem
./wp-content/plugins/updraftplus/includes/cacert.pem
./wp-content/plugins/updraftplus/vendor/guzzle/guzzle/src/Guzzle/Http/Resources/cacert.pem
./.wp-toolkit_v/wp-content/upgrade-temp-backup/plugins/wordfence/vendor/wordfence/wf-waf/src/cacert.pem
./.wp-toolkit_v/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/cacert.pem
./.wp-toolkit_v/wp-content/plugins/updraftplus/includes/cacert.pem
./.wp-toolkit_v/wp-content/plugins/updraftplus/vendor/guzzle/guzzle/src/Guzzle/Http/Resources/cacert.pem

Although this action has removed the problem, it would be good to know: –

a) what caused the issue? I only noticed the problem when I logged on to the admin pages. If I hadn’t, it could have been there for days, until I next happened to log in.

b) why was it looking for a file, that presumably it isn’t looking for now that I’ve deactivated/activated the plugin?

Checking the logs on https://cleantalk.org/my/logs_mscan does suggest it’s got confused. It shows a recent scan has completed – but on the other WP site and I didn’t start a scan on there.

I will log out of the other site and try again on this site and see what happens.

All steps run.

Running the scan now.

@gappiah – thanks for the reply.

The problem I have though is that index.php shouldn’t redirect. The only URIs that should redirect are either a single / or nothing (as per the apache RewriteRule. It searches for ^/?$ which means just a front slash, which is optional.

# php -- END cPanel-generated handler, do not edit
RewriteCond %{HTTP_HOST} ^thepompeychimes\.net$ [OR]
RewriteCond %{HTTP_HOST} ^www\.thepompeychimes\.net$
RewriteRule ^/?$ "https\:\/\/thepompeychimes\.net\/forum" [R=301,L]

Before I installed WP, I had an index.php file and that didn’t redirect. I renamed that file index_pre_wordpress.php before I installed WP. That still doesn’t redirect. All the other files in the directory do not redirect. It’s just the newly created WP index.php that does. That’s what makes me think it is something going on in the background, where WP is stripping the index.php bit, which then does get picked up by the RewriteRule.

I have tested this just now. If I comment out the RewriteRule in .htaccess and enter https://thepompeychimes.net/index.php, nothing redirects and I see the WP home page. If I then put the RewriteRule back, https://thepompeychimes.net/index.php redirects to https://thepompeychimes.net/forum/. No other file redirects.

I think I’ll have to look around and see if I can create a rewrite that does the following. I’m sure it must be possible and then it simply won’t redirect me. It won’t be too much hassle to update the .htaccess file if my ip address changes: –

If ( 
      (host is thepompeychimes.net OR
       host is www.thepompeychimes.net)
      AND
      (ip address isn't my ip address)
    )
Then
  Redirect

I’ve just seen the following on https://quic.cloud/faq/#cache, which may have an impact in what I’m seeing: –

Under the current CDN cache policy, pages are stored at a PoP for 24 hours from the last access. So, pages that don’t see much traffic will be removed from the PoP’s cache after about a day, but pages that are accessed at least once daily will remain in CDN cache up to 7 days.

Future plans include tiered regional caching, which will increase the CDN cache hit rate and allow us to cache pages in a nearby node longer term.

I’ll try making sure I access the homepage a few times a day and see if the MISS goes away.