When you prepare manual update, then this user is a same, as from web-server. _ /var/www/rutorrent/share/users/webuser/settings/rss : and everything inside is owned by www-data _ /var/www/rutorrent/plugins/rss : is owned by www-data _ ps aux | grep rss : shows rss run by rtorrent user From your explanations Novik, everything looks ok to me. I agree indeed , but to be honest, all my plugins have always been owned by www-data and work fine so far. Surely with incorrect permissions or ownership it will either always work or never work and not as I have here "sometimes" work and then self heal. If this true, then this is a reason of rss auto update behavior.
For automatic update - this user is a same, as from rtorrent. Also, even with rtorrent user as the owner and relaunch of rtorrent and refresh rutorrent, it is still the same... Actually: ps aux | grep rss Doesn't show it running now... The container is available here if you wish to look deeper: https://github.com/linuxserver/docker-rutorrent However as requested: https://github.com/linuxserver/docker-rutorrent/blob/a9690d70072570d61f67e02866aaa077204d5707/root/defaults/ls -l /usr/share/webapps/rutorrent/plugins/rss total 124 -rw-rw-r-- 1 abc abc 8097 Oct 29 -rw-r--r-- 1 abc abc 237 Oct 29 -rw-rw-r-- 1 abc abc 107 Oct 29 -rw-rw-r-- 1 abc abc 429 Oct 29 drwxrwxr-x 1 abc abc 14 Oct 29 images -rw-rw-r-- 1 abc abc 50603 Oct 29 -rw-rw-r-- 1 abc abc 530 Oct 29 drwxrwxr-x 1 abc abc 262 Oct 29 lang -rw-rw-r-- 1 abc abc 375 Oct 29 -rw-rw-r-- 1 abc abc 3905 Oct 29 -rw-r--r-- 1 abc abc 35698 Oct 29 -rw-r--r-- 1 abc abc 330 Oct 29 [email protected]:~$ ls -l /var/www/rutorrent/share/users/webuser/settings/rss total 4 drwxrwxrwx 2 rtorrentuser rtorrentuser 4096 Nov 9 cache -rwxrwxrwx 1 rtorrentuser rtorrentuser 0 Nov 9 scgi_port = 127.0.0.01 encoding_list = UTF-8 port_range = 55000-65000 port_random = yes check_hash = no directory = /home/rtorrentuser/downloads session = /home/rtorrentuser/.session encryption = allow_incoming, try_outgoing, enable_retry schedule = watch_directory,1,1,"load_start=/home/rtorrentuser/watch/*.torrent" schedule = untied_directory,5,5,"stop_untied=/home/rtorrentuser/watch/*.torrent" use_udp_trackers = yes dht = off peer_exchange = no min_peers = 40 max_peers = 100 min_peers_seed = 10 max_peers_seed = 50 max_uploads = 50 execute = schedule = espace_disque_insuffisant,1,30,close_low_diskspace=500M corresponding date of directory for multi user. Sometimes (correct settings) it works, sometimes (incorrect) - no. Would you consider running the docker container linked above and having a look. I tried to change my rss folder's owner from www-data to rtorrent-user. It is the only folder here that's owned by www-data while the others are owned by rtorrent-user.
each POP maintains its own cache and timing on any given object we vary based on when that POP first accessed it.
There shouldn’t be anything special about an RSS feed in terms of expiring content from the cache; it should age out based on whatever expires header is set on the object at that pop and if a more updated version is available when the cache expires it should display it. I don’t have another post/feed coming out for a week to test this issue.
If you run curl -I https://com/blog/feed/ you’ll get the Cloudflare headers back and one of them will be the expires header…