You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What version are you using?
2.0.78 Wat OS are you running?
Windows 11 Pro, up to date Are you using Docker or as a service?
Service Which debrid provider are you using?
Real-debrid Which downloader are you using?
Bezzad Please attach a log file here with the log setting set to debug rdtclient - Copy (2).log
All the Post Download Action options are set to "remove download from client and provider" and yet after completion the log just says:
2024-05-31 07:09:16.233 -04:00 [DBG] RdtClient.Service.Services.TorrentRunner: Not removing torrents or files for torrent www.SceneTime.com - Station 19 S07E10 1080p HEVC x265-MeGusta (TEZHWNCZK2RTU - downloaded 100%) (425bc816-6f6a-429d-a509-f0b2a52bbff3)
The text was updated successfully, but these errors were encountered:
I had the same issue, but then there was a mis-configuration. If you're using docker, you need to make sure your "Download Path" and "Mapped Path" are correctly set. If they aren't, you should see a Warning on Radarr side telling that one path is inaccessible, in that case Radarr, itself will be unable to move the file and rdt-client will not remove the file.
What version are you using?
2.0.78
Wat OS are you running?
Windows 11 Pro, up to date
Are you using Docker or as a service?
Service
Which debrid provider are you using?
Real-debrid
Which downloader are you using?
Bezzad
Please attach a log file here with the log setting set to debug
rdtclient - Copy (2).log
All the Post Download Action options are set to "remove download from client and provider" and yet after completion the log just says:
2024-05-31 07:09:16.233 -04:00 [DBG] RdtClient.Service.Services.TorrentRunner: Not removing torrents or files for torrent www.SceneTime.com - Station 19 S07E10 1080p HEVC x265-MeGusta (TEZHWNCZK2RTU - downloaded 100%) (425bc816-6f6a-429d-a509-f0b2a52bbff3)
The text was updated successfully, but these errors were encountered: