How do I find the cause of the permanent PHP slot occupancy by output1-1.jpg HTTP/1.1?

EDIT 04.Okt.24: THE PROBLEM IS NOT SOLVED BY DELETING THE BROKEN IMAGES!

Hello Make Community!

On October 1st, I suddenly no longer had access to WordPress. The loading times were very long (about 6 minutes), just a white page. But after about 6 minutes, the page suddenly loaded very quickly. Customer service suspected a timeout problem.
Debug showed me some errors such as the plugins BackUpWordpress, Rank Math, Cometcache and 2 others. Deactivation didn’t help, though. Now that everything is working again, I get a message from customer service with the following content:

Hello Mr…
For each account, only a limited number of slots are available for PHP processes in order not to overload the server. These slots were permanently occupied.

The reason for this was that the two domains “…de” and
“…eu” repeatedly called themselves (so-called
self-includes) and started php processes in the process.

The following was repeatedly called on both domains:
/wp-content/uploads/2024/09/output1-1.jpg HTTP/1.1
We have now prevented this by inserting the following lines into the “.htaccess” file in the root directory of the pages:

ALL-INKL.COM self-include protection BEGIN

order allow,deny
allow from all
deny from xx.xxx.146.151

ALL-INKL.COM self-include protection END

Please note that this is only a temporary solution to the problem, as it may cause your website to no longer function correctly. We were unable to determine what is causing the calls. Since it works the same on both sites, a plugin is probably the cause. We are happy to answer any questions you may have.

Kind regards
Customer service

When I saw this request, I immediately suspected where the problem could be coming from:

In this MAKE video: https://www.youtube.com/watch?v=i-BizXt4jdY, at around 13:36 min, it is recommended to make the name of the JPG file unique. Apparently I made a mistake.

I have now deleted all images with the name
/wp-content/uploads/2024/09/output1-1.jpg.
You can see that they are faulty (it is an empty image).

My question:

  1. What do the professionals think, can I simply switch off the ALL-INKL.COM self-include protection again?
  2. What exactly happened?
  3. Is this a problem that should also be reported to Wordpress?

Thank You

Frank

Deleting all images created in this way solved the problem. There were also images that you could not see were defective.

2 Likes