Do you happen to own Feeds API as well?
no unfortunately
Your problem is something completely different. I even tested your feed with older versions of Feeds and it still fails. RSS parser is getting an HTTP error from your server when trying to fetch the RSS feed. I am not sure what could be causing this. Are you aware of anything else that has changed?
I shipped an update that will output more details to the PHP error log when something like this happens. Try that can let me know what is in the php error log on the server.
From what I know nothing has changed in my server, the rss data was displayed, then I updated FEEDS and published the page.
At this point the problem arose.
Now I updated php to 8.4, everything seems fine (if you tell me some parameters to check, I’ll check).
I updated FEEDS to 1.15.3 and published the page.
I also checked the site’s RSS on the “RSS Mobile” App,
it’s fine, it works and updates all posts, displaying date, title and image, even the link to the original page works.
So you updated your server to PHP 8.4 and it’s working now?
No
From April 6th this error
[06-Apr-2025 19:18:57 UTC] PHP Fatal error: Declaration of Feeds\Service\RSS::processUrl(string $url): void must be compatible with Feeds\Service\Service::processUrl(string $url, array $headers = []): void in /home/ua3y4nzt/public_html/rw_common/plugins/stacks/feeds/Feeds/Service/RSS.php on line 25
Since April 14th always this error
[16-Apr-2025 10:32:21 UTC] Feeds SimplePie Error: cURL error 92: HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1)
The first error was the one that I shipped an update for. That is definitely fixed.
The 2nd error is one that I get for your RSS feed as well. I was hoping that possibly fetching the RSS feed from your own server would have better results.
I am trying to figure out what is unique about this RSS feed. I tested the RSS feed from the Poster demo and that works just fine.
I will continue digging to see if I can unearth some reason that your server is doing this.
1 Like
I figured it out… Your server is blocking connections with anything with a USER_AGENT that contains SimplePie. This is library that is used to parse the RSS feed.
While I can set a custom user agent for my request, I am unsure of the ramifications of that for everyone else. Would you be willing to ping your hosting company and ask them about blocking connections from SimplePie?
Thanks for the help,
yesterday I contacted my hosting company’s support to understand what was happening…
in fact, as a test I put the link of an rss of a demo site created with Poster2 by Stuart, and it works very well.
So I asked my host’s support what had happened/changed in early April.
I’m waiting for a response.
Let’s see what they answer and then I’ll let you know.
Thanks
Hi Joe, I contacted support, they told me that the meaning of the error indicated and a possible cause of the block could be the firewall, so I disabled the firewall.
Unfortunately the error remained, so their advanced support contacted me by sending me an email.
I sent you a message with the email they sent me.
Can you take a look?
I didn’t understand well, they prepared a script that simulates what simplepie does in a separate page.
Thanks
The host support clearly does not understand the problem. They are clearly blocking any request that has SimplePie in the User-Agent of the request.
Works (user agent not set)
Broken (user agent set to SimplePie)
The following code can be used to trigger the error.
<?php
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://gianluca.online/blog/?feed=rss');
// Comment this out for it to work
curl_setopt($ch, CURLOPT_HTTPHEADER, ['User-Agent: SimplePie']);
$response = curl_exec($ch);
if (!$response) {
die('Error: "' . curl_error($ch) . '" - Code: ' . curl_errno($ch));
}
echo 'HTTP Status Code: ' . curl_getinfo($ch, CURLINFO_HTTP_CODE) . PHP_EOL;
echo 'Response Body: ' . $response . PHP_EOL;
curl_close($ch);
?>
I honestly have no idea what to do as they tell me it’s not their problem.
Tomorrow I’ll completely delete the site and publish everything from the new one.
If unfortunately it doesn’t work, I’ll remove the FEEDS.
Thanks Joe for your help and interest in the problem.
Hi, @Gianluca. That’s a good call. Whenever something does not work that used to, the first thing to do is to republish all files and then re-upload to server at least the rw-common folder.
Wiping the server and republishing will not help at all. The support engineer placed a PHP file on your server in an attempt to show you that curl works with the RSS feed. However, they did not understand the problem and did not use the proper code.
The PHP code that I place above illustrates to them what the issue is and that their server configs are blocking the request. Send them that code and tell them that if they run it, they will see the issue.
1 Like
ok, thanks, I’ll try to send it to support, let’s see if they understand something.
Thanks