Closed shulymn closed 1 month ago
Sorry posting right after my initial post but I wanna add an important detail :
I switched to alldebrid temporarily and everything works fine, the problem most likely comes from real-debrid, as i said probably a change in their API?
That's a temporary solution, ideally i'd like to use Real-debrid back if possible
Thank you.
Edit :
Found this on twitter
yeah this change some of their api endpoints seems like RDT client need to use these new ones? not sure
yeah this change some of their api endpoints seems like RDT client need to use these new ones? not sure
Yes the api endpoints need to be changed. The default settings of rdtclient are pretty light (3 to 6 requests per hour) so I doubt rdtclient is a problem and needs to change anything on this side. Just the api endpoints should be enough
I was just about to post the same. Same "internal error" here...
Same issue
my torrents disappeared in RDTClient too
Pretty sure the dev also will need to add a 1 second delay between calls especially for getting the links, as it can trigger a fair_usage violation it seems like if it pounds the server for all the files at once.
honestly just needs to have some logic added to deal with the new api limits ASAP.
same I hope the dev is already working on it, everything is stopped and I cant do anything
I was previously getting this "Internal Error", and I could Start Torrent on real-debrid's site, and it would download.
However, I just sent a couple more files through on Radarr since I saw the real-debrid team just said they're fully functional - both files worked.
Maybe the RD api just wasn't fully functional yet? Can anyone else confirm if theirs are working again? I don't know how rdt-client interacts with the torrents api and if we should expect it to be broken or not.
Now it gets stuck into "Torrent waiting for file selection" Sometimes it switches to "Too many requests" It eventually ends up downloading though !
A fix is probably needed in the number of requests and delay between them or something as well, but yeah it works again
+1 My torrents are disappearing. It doesn't seem to be handling the rate limit correctly.
Again I don't know how this works exactly but if you don't need your torrents stored in RD, it might be worth clearing them if you're being rate limited, and see if that helps until rdtclient is updated. I previously received a rate error (that also eventually did download) - but after I cleared my torrents list in RD, no errors, straight to downloading after file selection.
For example, perhaps rdtclient pulls all /torrent api results, hitting a 250/s rate limit on rd, and if your RD /torrents was flushed, perhaps that would be fixed (until you hit another 250 cached)
If you're using something like Debrid Media Manager, this might not be feasible, but if you just use torrents for one-off downloads like RDT-Client > Radarr, maybe it is.
I don't know how it works either but I think it's a good idea to not keep torrents on real-debrid for that issue, it was always setup like this for me anyway. I think my "too many requests" came from the fact that I was trying different torrents at that moment. Since yesterday, it downloaded what sonarr sent without any issues
+1 My torrents are disappearing. It doesn't seem to be handling the rate limit correctly.
I am seeing this too. I turned on debug logs. Looks like it could be on RD side:
System.Exception: Unable to deserialize Real Debrid API response to List
1. Response was: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
Seems like it stucks at "Torrent finished, waiting for download links", so it doesn't tell Radar/Sonarr that files are present because they're not added into the symlink folder after the download.
Indeed, the /torrent endpoint changed on RD API side, let's see if this can be fixed anytime soon here :D
Has anyone tagged @rogerfar so he is aware of the potential change requirements set by RD
I'll have a look later today
I saw on X that everything should be back to normal right now, is that the case?
I saw on X that everything should be back to normal right now, is that the case?
A few endpoint responses changed and rate limits were introduced on the API, but I don't think any that impacts the functionality of rdt-client.
If people are having issues, they are likely rate limited due to how they are mounting their drives.
It probably wouldn't hurt for people to raise their "Check Interval" within rdt-client, but I don't believe rdt-client polls nearly enough to trigger the limits on its own.
I tried to make some changes to RDT to not keep calling the /torrents/{id} endpoint for each torrent, by just using the /torrents
endpoint and use that data for processing. Issue is that the status
field isn't updated until you call the /torrents/{id}
endpoint, so you have to keep polling.
What I can do is simply ignore torrents that are completed to limit the amount of requests.
I pushed 2.0.80 to should fix those issues.
I pushed 2.0.80 to should fix those issues.
I checked portal and get warning I am running .79 and .80 exists. I forced a docker compose rebuild update and on portal it doesn't tell me I have an update anymore but help screen still shows .79
I pushed 2.0.80 to should fix those issues.
I checked portal and get warning I am running .79 and .80 exists. I forced a docker compose rebuild update and on portal it doesn't tell me I have an update anymore but help screen still shows .79
Mine works without issue after update and doesn't show the mismatched version number as described. Recommend checking again making sure you're running the correct image.
@rogerfar Hi, I know this is off topic but when using zurg nightly with RDT client is there any hope that I can download music? I know real debrid rar it but according to zurg they unrar it so can rdt client use symlink downloader after that?
@rogerfar After updating to 2.0.80, I am able to download again, but have an issue with the GUI. The Torrents tab shows what I'm guessing is all past download links as "unknown status" with the current download showing at the very bottom (see attached picture). The page usually locks up and crashes. Also, I no longer see a progress bar in radarr/sonarr while a file is downloaded.
Below are the container logs. The "out of memory" exceptions and "time-out" exceptions begin once a file is selected in radarr/sonarr. I've never had a memory issue for this vm until these recent rd changes.
[15:23:50 WRN] Starting host on version 2.0.80.0
[15:23:52 INF] TaskRunner started.
[15:23:52 INF] ProviderUpdater started.
[15:23:54 INF] UpdateChecker started, currently on version v2.0.80.
[15:23:54 INF] WatchFolderChecker started.
[15:24:16 WRN] 304: /index.html
[15:24:17 WRN] 101: /hub
[15:24:26 WRN] 304: /index.html
[15:26:10 WRN] 304: /index.html
[15:26:17 WRN] 101: /hub
[15:26:31 WRN] 101: /hub
[15:27:12 ERR] Exception of type 'System.OutOfMemoryException' was thrown.
System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at System.GC.AllocateNewArray(IntPtr typeHandle, Int32 length, GC_ALLOC_FLAGS flags)
at System.Buffers.SharedArrayPool1.Rent(Int32 minimumLength) at DownloaderNET.Downloader.Download(Int64 thread, Chunk chunk, CancellationToken cancellationToken) [15:27:20 ERR] Exception of type 'System.OutOfMemoryException' was thrown. System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown. at System.GC.AllocateNewArray(IntPtr typeHandle, Int32 length, GC_ALLOC_FLAGS flags) at System.Buffers.SharedArrayPool
1.Rent(Int32 minimumLength)
at DownloaderNET.Downloader.Download(Int64 thread, Chunk chunk, CancellationToken cancellationToken)
[15:27:20 ERR] Exception of type 'System.OutOfMemoryException' was thrown.
System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at System.GC.AllocateNewArray(IntPtr typeHandle, Int32 length, GC_ALLOC_FLAGS flags)
at System.Buffers.SharedArrayPool`1.Rent(Int32 minimumLength)
at DownloaderNET.Downloader.Download(Int64 thread, Chunk chunk, CancellationToken cancellationToken)
[...]
[15:27:31 ERR] Exception of type 'System.OutOfMemoryException' was thrown. System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown. at System.GC.AllocateNewArray(IntPtr typeHandle, Int32 length, GC_ALLOC_FLAGS flags) at System.Buffers.SharedArrayPool`1.Rent(Int32 minimumLength) at DownloaderNET.Downloader.Download(Int64 thread, Chunk chunk, CancellationToken cancellationToken) [15:28:01 ERR] The operation has timed out. System.TimeoutException: The operation has timed out. at DownloaderNET.Downloader.Download(Int64 thread, Chunk chunk, CancellationToken cancellationToken) [15:28:13 ERR] The operation has timed out. System.TimeoutException: The operation has timed out. at DownloaderNET.Downloader.Download(Int64 thread, Chunk chunk, CancellationToken cancellationToken) [15:28:13 ERR] The operation has timed out. System.TimeoutException: The operation has timed out. at DownloaderNET.Downloader.Download(Int64 thread, Chunk chunk, CancellationToken cancellationToken) [15:28:13 ERR] The operation has timed out. System.TimeoutException: The operation has timed out. at DownloaderNET.Downloader.Download(Int64 thread, Chunk chunk, CancellationToken cancellationToken)
On my side still on 2.0.80, auto downloading doesnt seem to work anymore, I have to manually start the torrents from RD.
Also, while completed, torrents get stuck on : "Torrent finished, waiting for download links", so my -arr apps aren't processing the complete download.
Could you tell more about your setup? How are you mounting your drive? rclone_rd or zurg? It's likely something else is flooding RD's API and the selection API calls are getting rate limited.
Could you tell more about your setup? How are you mounting your drive? rclone_rd or zurg? It's likely something else is flooding RD's API and the selection API calls are getting rate limited.
Yeah i'm using zurg since the api changes.
I set limits on zurg config.yml tho ! Is there a setting that I can setup on rdt side also ?
It works fine for me since the update, here are the settings i'm using :
Also make sure your torrent list is empty on real-debrid side, i don't know if that changes anything but that's how it is for mine.
I got the same as yours, even put a bigger check interval, and files are still not selected nor the torrent set as compelted and stuck on "waiting for the download links".
I had similar issues since RD issues, latest update was still having weird issues, like the eternal long white page of checkboxes. Finally I found it was caused by the .db which was broken, which notmally is a few KBs it was 80MBs, with lots of dead or repeated torrents. Deleting the db and starting clean fixed all issues.
Which brings one point, maybe settings should be saved in a text file to avoid losing configs when the db is corrupted, broken or deleted.
I had similar issues since RD issues, latest update was still having weird issues, like the eternal long white page of checkboxes. Finally I found it was caused by the .db which was broken, which notmally is a few KBs it was 80MBs, with lots of dead or repeated torrents. Deleting the db and starting clean fixed all issues.
Which brings one point, maybe settings should be saved in a text file to avoid losing configs when the db is corrupted, broken or deleted.
Might help then, I reinstalled rdt client entirely when I started having the issue, so that might help
I will add another check to force update torrent data when no filename is found in the DB. This should solve that issue.
Seems that this is pretty stable now.
What version are you using? 2.0.79 (also tried downgrading to 2.0.78 no success) What OS are you running? UnRAID Are you using Docker or as a service? Docker Which debrid provider are you using? Real-debrid Which downloader are you using? Aria2c Please attach a log file here with the log setting set to debug
This is what I get when I add any torrent, either manually, or using sonarr or radarr. This wasn't happening yesterday, last download I successfuly did was yesterday 11/07/2024 14:41:32 Nothing changed on my side since yesterday, I reinstalled rdtclient entirely just to see if it fixed it but nothing. This happens because the torrent doesn't get automatically started on real-debrid, when i go to the page of real-debrid, it asks me to select the files and gets stuck here. If I select files and accept, the torrent starts downloading on rdtclient. Something might have changed on real-debrid APi, maybe. Here are some more screenshots :
Before starting the torrent manually on real debrid : After clicking "start my torrent" on real-debrid :
Thanks for your help and your work.