Refusing to invoke method checkforupdates of handler RPC with invalid CSRF token.

[Organizer21]

Hi again, thanks for solving that "older" issue, I had to find a workaround at the time and did not noticed it got resolved at the time.

Now, I'm not sure if you've run into this issue yourself, I seem to be running:
Tiny Tiny RSS v25.08-f7fc0032 © 2005-2025 Andrew Dolgov

I accidentially updated my TT docker images this week... and yeah, something had to crash of course. I also lost some custom changes I had done to select original files but I can only blame myself for not backing up and/or implementing in a "plugin" way.

Anyway, not sure what Andrew changed, it's hopefully something basic and easy to fix. However as non-coder myself, I've tried and failed to resolve it so far. When heading to the Feedcleaner TAB I see message like this:

Refusing to invoke method checkforupdates of handler RPC with invalid CSRF token.

1. backend.php(168): user_error (Refusing to invoke method checkforupdates of handler RPC with invalid CSRF token.)
2. Real IP: 1.2.3.4 Forwarded For: 1.2.3.4 Forwarded Protocol: https Remote IP: 172.20.0.1 Request URI: /tt-rss/backend.php User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/139.0.0.0 Safari/537.36

Would you be able to update yourse and have a look, since ithe updates overwrote my installatioon I am pretty sure it should be easily reprocuded, though I an also look to do a new installation only running feedcleaner to validate in case you think it's beyond a feedcleaner issue.

[wltb]

Yes, I'm a bit behind. I hope to update my instance in the near future, but there is no ETA.

Regarding the error message/stack trace, I'm afraid I don't know what the problem is or how to fix it. I'm pretty sure that the plugin doesn't call the checkforupdates method itself.

Does the plugin still do its job, and editing the config is possible, and this error only shows up once on switching to its tab, or is there some other malfunction?

[Organizer21]

That’s a brilliant question — and a really important one. Honestly, I’m not sure why it didn’t even occur to me to check that earlier.

Some good news on that front: at a glance, while the Feedcleaner admin tab (and tester) does NOT work. The actual cleaning still seems to trigger when I debug a feed, so that part of the functionality seems intact.

YES - Feedcleaner tab shows in Admin
NO - Feedcleaner tab shows config and allows editing of config
NO - Feedcleaner tab shows the Test Tab
YES - Feeds are being cleaned when fetched

I have no further errors showing right now in the system log, though I tried to use CoPilot to hack around to fix the admin view, so I need to check if I am running the vanilla again or a version with some edits.

So the issue needing fixing seem to be on the admin side only.

[wltb]

OK. If you find anything else that might be helpful, report it here. I'll try to investigate the problem as soon as I can.

[wltb]

Skimming over ttrss'es source code gave me no epiphany, but a suspicion what could cause the problem. I'll update my instance as soon as I can, and I hope this can be reproduced and fixed.

[Organizer21]

Thanks, that would be awesome. Not sure if you can see it or would need update to the latest in test instance to see what might have broken or not.

I've been thinking about updating two other TT-RSS instances I host to the latest version, but I'm hesitant since I rely heavily on this plugin — it fixes way too many feed issues across the board 😅. As I mentioned, I believe the issue was limited to the admin interface, but I just restarted my NAS and happened to check in on the UPDATER container in Docker.

Are these FeedCleaner log notes something I should be concerned about (attached a more complete log section)? At a glance, they look like debug logging—I don’t recall enabling that, but the logs are pretty noisy and the same messages seem to repeat over and over. Unless it’s something specific to my setup, I’m guessing it might be related to the recent accidental update to the latest images. As you know, I’m currently running a fairly clean stock version.

2025-09-18T09:37:16.798180930Z [09:37:16/143] 1. plugins.local/ff_feedcleaner/init.php(40): user_error(FeedCleaner init() running — 1.6 debug)
.......
2025-09-18T09:37:17.935672576Z [09:37:16/143] 1. plugins.local/ff_feedcleaner/init.php(47): user_error(Handlers after registration: PluginHost Object
.......

ttrss_updater_logs.txt

[wltb]

I suspected that the problem is related to PluginHost, but I'm afraid I can't tell you from your log file if I'm right.

Anyway, I'm on it and hop to solve this in the next few days.

[wltb]

Sorry that it took me so long, I got a cold, and the static analyzer shat itself over the autoloader changes.

Anyway, the autoloader stuff caused some trouble with the UI, but these are fixed now. I'm not sure if this also solves your problem – I'm still a bit behind on upstream – so report back please.

[Organizer21]

Appreciate the follow-up and no worries at all, as per my late response now... I've been busy for various reasons as well. I'll be giving the update a go shortly and report back on what else might need attention.

[Organizer21]

Just replaced my old files with the new version, and I can once again access the Feedcleaner tab and edit/save the list. The Diff Preview also seems to be working, which is great news. I’ll keep an eye on the system log, but at first glance everything looks promising 👍

[wltb]

Glad it worked out well. Feel free to close this issue whenever you like.