PHP script using too much memory

I took a quick look at the site URL mentioned in the error above…

It says your site is blacklisted with malware… did you know that?

It’s possible the malware is clobbering your memory allocation.

If I’m right about the domain name then you might want to fix the site by scrubbing out all the malware.

@von44

I just checked it through here as I had that Sucuri link up anyway!

https://sitecheck.sucuri.net/results/https/monetizingonline.com

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

Late last night I pointed my little web crawler at your site.

There are several redirects probably due to building internal links and then setting permalinks after that.

There’s also a lot of 404 errors… that kind of stuff takes some horsepower to deal with.

If it was my site I’d double-check the links… get rid of the ones that don’t use the permalinks in favor of the proper permalinks. Menus are a very good place to look but some of the ‘read more’ links on your blog items (the loop pages) are broken.

As to the site itself security wise, I still suspect you might have some issues there.

Why not install IthemesSecurity and WordFence together and let them help keep an eye on attack items and security. IthemesSecurity and Wordfence play well together and complement each other.

I’d also install the Sucuri plugin and run it for a little while just to see if it finds anything. Then disable it but I always leave it installed in case I need to double-check things again.

I’d also recommend running the Broken Link checker plugin… That might help you get a grip on the 404 errors and keep things inline if you’ll pay attention to it. After a few days, you can throttle that back from its default 72 hours to 480 hrs. That thing can be quite a resource hog at times but 480hrs seems to work fine for me.

Normally, I’d recommend running CloudFlare but your site has response issues. Cloudflare tends to amplify those.

I also took a look at your DNS records. I don’t see a Cname record but the DNS test I then ran said you have one. Your host may have munged their DNS servers to do that but I was also wondering if your htaccess might be ‘belching’ out ‘www’ and then forcing WordPress to deal with that. I can’t tell from here but you might look for that or your site settings in the dashboard being set to ‘www’.

One more thing that might help would be to add a plugin such as Cache Enabler just to have something that works well to handle cache flushing.

It’s also possible that your site doesn’t get enough traffic to run the WordPress pseudo-cron… I usually run an external cron to force WordPress to better keep up with cron tasks.

Finally, if you continue having issues with this server, you might just engage a new server from your same host and migrate everything to there then cancel the old server.

I say do that on your own initiative as your host will probably balk at the idea or break that somehow to lessen the effect. Doing it on your own forces a random selection of new server and forces the complete migration where the host might otherwise leave things as they are and just move pointers and such to humor you.

Not that I’m accusing your host of doing that but ‘it’s so easy to do that kind of stuff’. I usually move servers within the same host after three years on shared hosts. On the Cloud hosts I haven’t seen the need…

I certainly hope something here might help you get to the bottom of all this.

Once you get the problem solved I’d recommend going to Cloudflare.

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

I’m overwhelmed with 404s on your site and I think I’ve tracked that down to an issue with your Google Analytics plugin and the code it’s jamming into your pages.

If you’ll shut down that plugin I’ll run this thing again and see if I can figure out the redirect, if it is still there afterwards, and any 404s outside of that missing GA script code.

Then we’ll take a look at that GA plugin again.

I’m running something that crawl’s your website like a search engine would. The broken Link Checker just looks at the links as it goes along on a shorter timetable but isn’t seeing that broken relative link (and that might be an issue in my crawler).

Did you throttle back the Broken Link Checker? I always recommend running that at 480 hours instead of its default 72 hour setting… once it has ran one time setting it to 480 hrs saves some horsepower and it seems to be able to keep up with everything just fine.