James Lee

@leorw It’s not the Blocksy Companion plugin, it is the Blocksy theme. The issue occur with just the Blocksy theme >v2.0 and Stackable installed.

Not localhost. PHP 8.1. WordPress 6.4.1.

@leorw, troubleshooted the same problem with my site and it appears to be a conflict with Blocksy theme version 2.0.0 and above.

Since Blocksy uses Freemius as well and they work very closely with you and Stackables, perhaps you can get in touch with their team and work out the problem? This should ideally be resolved quickly since many users are using Blocksy together with Stackables.

I’m seeing the same issue as well when I upgrade the Go theme to 1.3.7 in my staging environment.

As far as attacks, when I checked the logs there was no evidence of any.

What logs are you checking? Some attacks may not be logged at shared hosting account level and may only be logged at the server or root level.

Here’s a question. If I’m editing on via a desktop browser, why is there any XMLPRC activity? I thought that was for mobile devices. ??

Because they are not being accessed by you but by automated bots which are attempting to exploit XMLRPC of your website.

PID CMD CPU MEM
39579 lsphp:ome/[account stuff]/pickleballjourney.com/xmlrpc.php N/A 44
39580 lsphp:ome/[account stuff]/pickleballjourney.com/xmlrpc.php 15% 40
39712 lsphp:me/[account stuff]/pickleballjourney.com/wp-cron.php N/A 26
39750 lsphp:ome/[account stuff]/pickleballjourney.com/xmlrpc.php 41% 23

As you can see above, the XMLRPC processes are eating up quite a lot of your CPU with one process using 41% and the other process using 15%.

This leaves very little CPU left for other operations of your website, which is why you may hit your CPU limit even by just editing a post.

You should definitely take actions to prevent further attacks to XMLRPC.

If you can’t disable it, consider putting your website behind CloudFlare which should help reduce the number of bots accessing your website.

The mentioned error doesn’t really make sense.

It is trying to allocate 140535624893016 bytes which is 140 TB!

Did you make any changes to your themes or plugins or updated them recently?

Doubling your CPU should definitely help.

Do keep us updated about this!

If disabling XMLRPC doesn’t help, you may want to consider upgrading to a higher plan.

A plan with 0.5 Core of CPU and 0.5 GB of RAM may work for a small WordPress installation but ideally you will want double of that if possible to run a production website.

Can you let us know how much CPU were being used for each of the file year you mentioned during the “Fault”?

You may be under an attack of some sort. Blocking access to WP-Admin and XMLRPC may help. Putting your website behind CloudFlare should also help.

Did you install or update any themes or plugins before the CPU spike happened?

Try checking your traffics to see if they are legitimate. You may be under some bot attacks. Placing your website behind CloudFlare should help in this case.

It does sound like something at the server level is changing your file permissions.

You’ll need to check with your hosting provider to see if they know what is doing that.

If your WordPress installation is under “https://www.kellyethompsonart.com/gallery/”, your Site URL should be set to “https://www.kellyethompsonart.com/gallery/” as well.

As for the “Future home of something quite cool.” page, check and see if it is just an index file in your “/public_html” directory.

What WordPress version are you using?

You may want to try installing the Classic Editor plugin and see if that works:-
https://www.ads-software.com/plugins/classic-editor/

Google takes its own sweet time to index pages and not all pages may be listed in Google immediately.

There’s nothing much you can do but you can make Google’s job easier by:-

• Having a proper sitemap for your website.
• Making sure your robots.txt file is not blocking Google’s crawlers.
• Making sure your server is up all the time as search engine crawlers may not crawling your site if they keep facing issues connecting to the site.

One helpful tool that you can use is Google Search Console:-
https://search.google.com/search-console/about

If everything works fine after disabling the Yoast plugin, this indicates that the plugin is either at fault or it may be incompatible with your theme or other plugins.

Did you do anything before you see this error?

You may want to try reinstalling the plugin to ensure that there are no corrupted files within the plugin.

If it still doesn’t work, you may need to go to the plugin’s support section to seek support from the plugin developer and other users.