David LeBlanc

Hello @zachar25

You may want to try the GOTMLS plugin. I use it to clean up sites that have been infected and so far it’s worked very well at identifying and quarantining malicious code. https://www.ads-software.com/plugins/gotmls/

There is a premium version, but from my experience, it’s well worth the money. You can routinely scan for malware and viruses, an array of settings to establish a firewall and brute force patch.

I am a happy user of this plugin and I don’t get any kind monetary reimbursement of any kind for recommending it. The owner if the plugin is good about support as well.

Good luck.

Dave LeBlanc

This is a check, as I understand it, placed in the core 6.1 update, whether you need or want object cache or not. That is happens whenever I run Site Health and it’s annoying.

It took awhile, but I finally found/understand what has been causing this issue.

If you really don’t want to see it, there is a filter you can add to the functions.php file to filter it out. I did and it’s not nice to see it. Whether it’s wise or not is another matter. You can find the filter on this page of make.www.ads-software.com announcing the introduction of this check into the Health Check tool. So far, it’s worked without issue for me.

New cache Site Health checks in WordPress 6.1

Pauline

Thanks for the reply. I will go through the list above and report back.

No, I do not have a maintenance mode plugin. Any recommendations?

• This reply was modified 1 year, 8 months ago by David LeBlanc.

Whoops, wrong plugin. I needed Embed Code. Sorry, wrong forum.

My face is red.

Thanks for the prompt reply, though.

Just pretend I was never here.

Eli, hello. This is a follow up to my original support request above.

The situation seems to be resolved and I have reinstalled your plugin. I think the issue was with Jetpack and I think the issue with Jetpack was/is the overworked servers at AT&T hosting not timely communicating with Jetpack servers.

In addition to the cURL error, I was also, randomly, getting these messages from the Site Health Tool.

Deactivating the GOTMLS plugin ended the cURL error, mostly, but there were others:

1. The scheduled event, jetpack_sync_full_cron, failed to run. Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended.

2. The REST API call gave the following unexpected result: (403)

3. The loopback request returned an unexpected http status code, 403, it was not possible to determine if this will prevent features from working as expected.

I was also getting occasional “cannot connect to database” messages. Those were fleeting and seemed to end by refreshing my screen. That makes me think the servers AT&T provides are overworked and underpowered.

Also, on the WordPress.com side, the site was not always syncing WordPress.com and occasionally. Sometimes I had to do it manually and even then sometime it was not communicating. I have never had that problem before.

Jetpack also started to prevent me from logging in to the admin area of the site after the last update, though the site was on the viewer end was functional. That was last straw time, and I deactivated and deleted the plugin.

Since then, it’s been running well, the error messages above stopped and I reactivated your plugin. Life is good again.

I am not going to pursue this with Jetpack support because for me the problem is resolved. Jetpack and AT&T Hosting don’t like each other.

To be fair to Jetpack, I use it a lot and have not had a problem with it, at least not a problem like this.

The GOTMLS plugin now seems to be functioning smoothly, no issues, and I am happy.

Thanks for the prompt replay, Animesh. I will go through the troubleshooting part.

A apologize for the late reply.

Site URL: https://www.ism-houston.org

Thanks in advance for any help you can offer.

Also, I have also deleted and reinstalled Jetpack and reconnected the site through WordPress.com. I happens when I connect to WordPress.com. The key seems to not connect to WordPress.com, which makes the plugin useless.

I have the same issues. I am getting this message. “There has been a critical error on this website. Please check your site admin email inbox for instructions.”

The only way I can reconnect is to rename the Jetpack plugin (jetpack_x)

I have uninstalled and reinstalled the latest Jetpack plugin and disconnected and reconnected WordPress.com. The only thing that let’s me back in is either removed Jetpack completely or rename in the plugins folder via FTP, which is what I did.

The site is running okay.

A refresh and hard reload does not solve the problem either. I first noticed it trying to trouble shoot one performance issue the Site health tool was giving me: The scheduled event, jetpack_sync_full_cron, failed to run. Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended.

I don’t think that has anything to do with it. It’s been an intermittent performance issue for a while now the hosting service the site is on now, AT&T.

Eli, thanks for the reply.
Below is the information you asked for and if you need anything else, let me know.
Looking at this list, I realize I have to do some reorganizing and drop some of these.

Active plugins

• Advanced Image Styles
• All-in-One Event Calendar by Time.ly
• Anti-Malware Security and Brute-Force Firewall
• Autoptimize
• Embed Code – Insert Header & Footer code
• Enhanced Text Widget
• Envira Gallery Lite
• Jetpack
• Page Builder by SiteOrigin
• Redirection
• Server IP & Memory Usage Display
• Simple Image Sizes
• Spacer
• WP Fastest Cache
• Yoast SEO

Inactive plugins

Duplicator

Current version of WordPress: 5.9.2

PHP Version: 7.4.19@64bitOS

nlpro, thanks for the reply.

Yes, it reproduces on the latest release of the plugin.

Sorry, not going to set up the debug to true. I got fed up dealing with this conflict (and others) and deleted the plugin. I am doing this on all my sites.

I couldn’t delete it in the plugin manager, the conflict seemed to prevent that. I had to delete it via FTP and then go remove it from database.

Really, this was a final straw kind of thing for me. Lately, it’s one thing after another it seems and I am tired of wasting my time on it. Right now I am just using the security features in JetPack and keep everything updated. Not even sure a security plugin like iThemes is worth it now.

Hello. I am getting the same problem. Did you find a fix?

Yep.

@ashmozza89, If it helps any, that Google is not using your meta description is good. It thinks content on your page is better answer to a query than you meta description. That is not a bad thing. That’s good.

Google and Bing and the others do this all of time. The search engine understands your page and wants a user to view it to answer your question. Be proud. Your content is good.

Gal,

Hello and I apologize for the late reply. Yes, that is what I did and it’s working as it should.

I use this plugin on other sites and did not have the same issue with it, so it was something peculiar to this site or it’s host. I tried to update another plugin yesterday and had the same issue as with this plugin.

The fix was simple, just delete the old folder and up load it again. Everything is working now.

Thanks.