

I've tried various 2xx responses codes to see if MCM is expecting a different response code, the only other thing I'm thinking it could be is that there is some payload response that MCM is verifying I have been scouring the internet to see what utorrents web ui responds with when the add-url action is to be performed but I cannot find anything usefull, all I can find is what the query string should look like.ĭoes anyone know what MCM is expecting in the response from utorrents web interface, if I can properly generate that, then I think I have a working work-around. I'm using the standard download manager application that comes with the Synology DSM 5 software.

torrent files, it then picks this up and proceeds to download. I then run an external Magnet2Torrent python script which converts the magnet url to a torrent file, my nas has a scan directory for.

I just wrote my own one in python, but i'm having issues with MCM reporting that the submission has failed even though I see the full query string being submitted.
