Bad response from server: (400) Writing to rTorrent session directory failed, make sure it is writable for the ruTorrent user.

[perfect7gentleman]

I try to rename torrent but it give me that error

[26.03.2020 20:00:06] Bad response from server: (400) Writing to rTorrent session directory failed, make sure it is writable for the ruTorrent user.

[perfect7gentleman]

from nginx error_log

2020/03/26 20:04:30 [error] 7920#7920: *1606 FastCGI sent in stderr: "PHP message: PHP Warning:  file_put_contents(/home/USERNAME/.rtorrent_session//9E6EABDBF7470E084FD9BFD88B5DD09DDE6EC171.name): failed to open stream: Permission denied in /var/www/localhost/htdocs/rutorrent/plugins/rename/rename.php on line 17" while reading response header from upstream, client: 192.168.88.11, server: , request: "POST /plugins/rename/rename.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.88.9:88", referrer: "http://192.168.88.9:88/"

[Fleshgrinder]

I decided to place the files for the name alongside the torrent files of rTorrent in rTorrent's session directory to simplify integration with rTorrent scripts. This means that your rTorrent and ruTorrent must both have access to the session directory of rTorrent.

Ideal would be to store the name in a d.custom.name. Perfect would be if ruTorrent would support that right through the torrent creation form because then the name would be available to all scripts and everything from the beginning.

In any event, right now the session directory must be accessible.

[Fleshgrinder]

Let's keep this issue open because it's something that I definitely want to investigate. I think that the ideal described above is possible, the perfect would require patching ruTorrent that's for sure. However, I'm seriously thinking about creating an ruTorrent alternative because it's so bad...