bobcaswell

Hi @amandato, the issue started independently of any upgrade (we didn’t upgrade at first but then figured, why not, but that didn’t resolve anything). To me, it seemed like an overnight thing, but perhaps there is/was something with our feed that broke the camel’s back, so to speak, but that was a problem inevitability waiting to happen. We crossed the 300 episode mark probably around six months ago, and maybe we were just lucky that it took as long as it did to become a problem.

@amandato Apologies for the delay, and thank you! Those changes you suggested didn’t work as long as I kept the feed at 300 (which is what it’s been at for nearly a year now). I’m not sure what changed overnight to cause the persistent crashing. That said, keeping our podcast feed alive and well is more important than being stubborn about having it show 300 episodes. ?? So we’ve lowered it to 50 for now, and it hasn’t had any problems since then.

Our hosting provider is MidPhase, do you know them? Perhaps you could chat with them to see if there’s something they updated/tweaked on the backend recently?

Thanks!

Bob

Quick update, see below for the reply I got from our hosting. Does this help?

Thank you for your reply! Unfortunately we are unable to post on public forums. The only thing we can really try on this end is make sure your php.ini script limits are set correctly. This can definitely cause a problem with your plugins if it is not set properly.

Our logs do not show specifics on what is running with your plugins. The only this we are able to see is WordPress itself is trying to run processes which we pinpointed to your plugins folder.

I would check with the developer that built the plugin to see if they can provide at least minimum php requirements for it to load. If these are set to low they will cause issues like this for your site. Once we have those limits we will be able to verify if that is the case or not.

Hi Angelo,

Our podcast url/feed is https://infantsonthrones.com/feed/podcast/

A few more details: We have more than 300 episodes, and we have always let our feed include all of them (or 300 as is the max). And this scenario (i.e., the number of episodes being more than 300) has been true for nearly a year, so the question is, why all of a sudden did this crash everything overnight?

The short-term fix: We limited our feed to only the most recent 50 episodes, and that makes it so the plugin doesn’t overload the system (although it still uses a lot of resources compared to anything else running).

I’ve heard that the long-term solution (we can’t be the first podcast dealing with this) is to figure out how to run a caching plug-in with Blubrry, so I’d love any help / guidance / best practices for making that happen so that we can go back to sharing our full feed.

I’ll see if our host will give any more details, but based on that, any tips? Thanks for your help, been a fan for 5 years running!