ciudadnoticias

I imagine that it is the private IP of the server, why it was blocked, I don’t know, but I will monitor it very closely.
Of course count on that review and again thank you very much

Hello @hjogiupdraftplus
After having deleted the line in wp-config.php and having applied the 4 steps that you recommended in the previous message, I have the cron problem again, the scheduled posts are not published again.
I went to check the blacklist and there was an IP, which does not correspond to mine but I deleted it and now the cron is running, it seems that that blocked IP was the problem.
I think we can consider it solved, thank you very much for all the help provided.

Dear @hjogiupdraftplus
I put the line that you indicated in my wp-config.php and the cron works again, the entries are published, now my question is, if I leave that line in the wp-config the firewall would be disabled, right? So that solution wouldn’t work, would it?

Hello, thanks for answering.
WordPress cron is used to execute the task, we have already verified WP Control and when the task is not executed it remains “queued” if we let it run manually the task runs without problems.
Regarding the hosting provider, it says that there is no error, they say that the cron task is executed correctly, although now what it tells me about the 403 error yesterday in one of the messages they answer me this:

“While I review the Apache domlogs, I can see the next entry.

75.102.58.87 – – [2023/Oct/26:15:35:50 +0200] “POST /wp-cron.php?doing_wp_cron=1698327350.4555270671844482421875 HTTP/1.1” 403 0 “-” “WordPress/6.3.2; https : //citynews.es”
This log entry indicates that a POST request was made to “php/wp-cron.URL”, which was denied access by the server with a “403 Forbidden” status code.

Temporarily disabled ModSecurity for the website ‘ciudadnoticias.es’.
Please try again now.”

I tried it later but it didn’t work either, I don’t know if this can give more clues