Sonarr and Radarr error: Command "d.complete" is not allowed for untrusted connections.

[xombiemp]

Please complete the following tasks.

• Web browser cache cleared
• Link provided to install script if applicable
• Not using broken rtinst install script
• Web browser, ruTorrent, PHP and OS version provided

Tell us about your environment

ruRorrent: 5.3.3 with httprpc plugin
rtorrent: 0.16.14
Archlinux

Tell us how you installed ruTorrent

installed with Archlinux rtorrent AUR.

Describe the bug

Instead of trying to get ratio plugin working with 0.15.6 I just decided to update to 0.16.14. #3071
After I updated I started seeing this error in Sonarr and Radarr:
Command "d.complete" is not allowed for untrusted connections.

Looks related to this rakshasa/rtorrent#1710
I see that there are some settings in plugins/httprpc/conf.php

Should d.complete be added to the $XMLRPCProxySafeParams array?

I think I could also set $XMLRPCProxy to passthrough_unsafe, but I want to do this the right way.

It seems like Sonarr and Radarr are being thought of and SHOULD work, because they are mentioned in comments in the plugins/httprpc/conf.php file. Am I missing a config or something, or is something broken that needs fixing?

Steps to reproduce

Configure *arr apps like this

Expected behavior

No errors when communicating with rutorrent.

Additional context

No response

[simonc56]

Same issue (with logs) here :

• *arr : command "d.complete" is not allowed for untrusted connections crazy-max/docker-rtorrent-rutorrent#564

[simonc56]

Should d.complete be added to the $XMLRPCProxySafeParams array?

@xombiemp Can't you just try that in your config file ?

[xombiemp]

Should d.complete be added to the $XMLRPCProxySafeParams array?

@xombiemp Can't you just try that in your config file ?

Yes, I tried this and it did not work. However, setting $XMLRPCProxy to passthrough_unsafe did work and Sonarr connected successfully.
I wonder if this is the intended fix for *arr apps or if sanitize mode is supposed to work.

[simonc56]

This is not a rutorrent issue, but a rtorrent one.
Fix rakshasa/rtorrent#1853 has been merged, waiting for new rtorrent release.