Internal 500 errors caused by gp-premium plugin

Hello again.
I just checked another website that I have with another hosting (Dreamhost) in which I also have Generatepress installed.
I checked the equivalent urls. The same files on the other site that have the 500 error, also have it on this one. So it is not a server problem.
If it is of any help, I can share the settings and plugins of the two sites, or add the 171 urls that show the error.

Hi there,

can you test for other conflicts by temporarily disabling all other plugins, child themes or other custom functions you have on the site ?

Already did. It was the first thing the host asked me, but the problem continues. Also in the two sites I have different configurations and plugins.
The only plugins that are installed on both sites are:
GP-Premium
Rank Math
Shortpixel
WPForms Lite

Can you go to Dashboard > Tools > Site Health -- is there any errors/issues being displayed there?

Hello and thanks for the support.
In one it is "The optional module, imagick, is not installed, or has been disabled." (normal notification in WPX) and on the other site there is no notification.
Among others, the same errors on the two sites are:
https://citydogslife.com/wp-includes/update.php
https://mayagoded.net/wp-includes/update.php

https://citydogslife.com/wp-content/plugins/gp-premium/library/batch-processing/wp-background-process.php
https://mayagoded.net/wp-content/plugins/gp-premium/library/batch-processing/wp-background-process.php

It strikes me that the problem is in the two sites that are very different.

How old are the two sites ? As i believe that issue is related to the Old image resizer that GP used to use for the Featured Image resizing.

Can you share a screen short of the Customizer > Layout > Blog --> Featured Image settings ?

Hi.
One is 2 years old and the other about 7 months.
I'll send you the screen shot in a moment (let me find out how, I don't know how to do it)

By the way, I think you also have a similar problem:
https://generatepress.com/wp-content/plugins/gp-premium/library/batch-processing/wp-background-process.php

Hello,
Here are the screen shots of the Customizer> Layout> Blog -> Featured Image settings of both of my sites.
Site 1:
https://ibb.co/b2drZms

Site 2:
https://ibb.co/f0sxHSB
https://ibb.co/mCRLk7H
https://ibb.co/k4s49JC

Thank you

If you go directly to that URL (as you linked to above), you're going to get an error like that.

That file is used by our Site Library to run some background processes, but it's not intended to be navigated to directly.

Are you seeing any errors on your actual website as you use it, or is this error only happening when navigating to that file?

Hi,
It only appears when I open the url. Actually there are no problems on my sites.
I had an indexing problem in google (a lot of files were indexed from the wp-includes and wp-content/plugins/ directories).
When I made Google to crawl them again to de-index them, 171 new files in those directories appeared in Google Search Console with the error 500. When checking them directly, the error did appear.

Individual PHP files like this should not be indexed, as they don't have any content - they're purely functional files.

We can add a check in that file to make sure it can't be directly accessed, but if you have search engines indexing individual PHP files like this, you'll want to remove them from the index and make sure there are no links to them for search engines to follow.

The question I have is if having 170 files in the wp-includes directory with error 500 will not cause problems for my sites later?
Or even if the following files appear with error 500, will they not cause problems and will they work well?
Some of the files are:
https://citydogslife.com/wp-includes/update.php
https://citydogslife.com/wp-includes/widgets/class-wp-widget-categories.php
https://citydogslife.com/wp-includes/class-wp-http-requests-response.php

In case they do not give me a problem with this error later, I would be interested in adding a check in the files to make sure it can’t be directly accessed. Would they appear as 404?

These are all files you shouldn't be accessing directly - there's no reason to, and linking to them (when the links are set to follow) will index them in Google.

Your host may be able to block direct access to the files, but I'm not 100% sure.

I don't know if it will cause issues, but it would certainly be nice to keep your error_log empty so actual errors are easier to find.

Thank you very much for your support and patience.