rutorrent not found

[xino222]

good evening

I am currently using rutorrent version 4.2.6 (in docker) and I am getting error when adding it to homepage as instructed:

- rutorrent:
    icon: rutorrent.png
    href: http://192.168.1.75:8148
    description: 
    server: my-docker     
    container: rtorrent   
    widget:
      type: rutorrent
      url: http://192.168.1.75:8148
      username: false  #optional, false if not used
      password: false  #optional, false if not used

log error:

I was using version 4.0.2 before and it worked perfectly.

thx

[xino222]

no one? maybe rutorrent from version 4.0.2 onwards is configured differently in homepage?

I think I'll stay on 4.0.2 if I can't fix it...

thx

[xino222]

well, in case someone needs it, I have already seen what is happening, they have removed from version 4.0.2 (rtorrent) the httprpc plugin that is in the docker rtorrent in the path /var/www/rutorrent/plugins/httprpc

if this plugin is copied to the same path of the latest version of rtorrent the widget works fine in "homepage" but if the rtorrent version is upgraded to a higher one it deletes it and you have to copy it again.

edit:
I have verified that when restarting the docker, rtorrent DELETES the plugin httprpc from the directory where rtorrent has all the plugins: /var/www/rutorrent/plugins/httprpc

The only thing I have thought of is to create a scheduled task (in my case from the synology task scheduler although it can also be done from CRON) so that every 5 minutes it copies the plugin again:

docker-compose run cp -R /tmp/rutorrent/plugins/httprpc /var/www/rutorrent/plugins/httprpc

I hope this information will be useful to the homepage developers and they can fix this bug...

[github-actions[bot]]

This discussion has been automatically closed due to inactivity. See our contributing guidelines for more details.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.