Debrid provider rate limit reached...Processing paused until

[OnlyGoodGit]

The issue that I've been running into for the last two or three versions (there have been a few quick updates), is that I keep getting the yellow banner at the top that tells me that I'm over my Debrid rate limit and processing will be paused. I'm way under my limit with only 10GB downloaded and downloading directly from real-debrid works fine.

I have RDT Client setup as a service, but is the connection with debrid more stable with RDT on Docker?

What version are you using?
2.0.127.0

What OS are you running?
Windows 11 Pro 25H2

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
It looks like there are a ton of connection time out errors.

rdtclient_006.log

[OnlyGoodGit]

I think I figured it out. I was likely pinging real-debrid's api too many times per minute. They must have lowered their limit since I haven't changed my settings and have been downloading pretty steady for years. I increased the check interval to 30 seconds and it seems to have fixed it.

[TheTechRun]

I am having the same exact issue. I have been using RDT for many years now and now it's starting to do this. I switched to torbox from real-debrid and it's still happening.

[OnlyGoodGit]

Same here, it just started after I updated recently. Not sure if RDT Client is sending more individual API calls instead of batch calls or what is going on. For me, it was "fixed" by increasing Check Interval under Provider in the settings to 30.

[TheTechRun]

Same here, it just started after I updated recently. Not sure if RDT Client is sending more individual API calls instead of batch calls or what is going on. For me, it was "fixed" by increasing Check Interval under Provider in the settings to 30.

I spent quite some time today switching to decypharr and its working well. Thanks for the fix info. Will come in handy if I ever decide to change back.

[gcstr]

For me, it was "fixed" by increasing Check Interval under Provider in the settings to 30.

I bumped it to 120 and still see the error

[SquadCraftFTW]

having an issue with this when i'm doing the same stuff before updating to latest version of rdt client

[RomainHartmann]

Seeing this on v2.0.127 in Docker, so Docker vs Windows service isn't the factor.

Evidence this isn't a real RD 429:

• 2 torrents in the DB, Provider:CheckInterval=120, MaxParallelDownloads=3, so expected API traffic is well under the 250 req/min RD limit.
• Direct curl from inside the container with the same API key, same network, same moment as the Polly warnings: /user, /torrents, /torrents/activeCount, /hosts/status all return 200. 30 rapid-fire calls in a row to /torrents also return 200.
• netstat inside the container shows zero established connections to api.real-debrid.com while the Polly pipeline is still logging 429s.
• Polly Execution Time on the retries is ~10ms, too short for a real HTTPS round-trip (direct curl averages 100-200ms).

Typical log line, constant at ~4-6 per minute:

[09:44:54 WRN] Execution attempt. Source: 'RdClient-rd_client_handler//Retry', Operation Key: 'null', Result: '429', Handled: 'True', Attempt: '0', Execution Time: 10.4ms
[09:44:54 WRN] Resilience event occurred. EventName: 'OnRetry', Source: 'RdClient-rd_client_handler//Retry', Operation Key: 'null', Result: '429'

Fast execution time + no outbound TCP connection + all direct calls returning 200 suggests the Polly pipeline is generating synthetic 429s from something local (timeout short-circuit? stuck internal rate limiter?) rather than actually calling RD.

Environment:

• rdt-client 2.0.127 (rogerfar/rdtclient@sha256:f10b0891..., image built 2026-03-15)
• Docker on macOS (linux/arm64)
• Provider: Real-Debrid, premium account
• Downloader: Bezzad
• Settings: CheckInterval=120, MaxParallelDownloads=3, ParallelCount=8, Timeout=10

Downloads still succeed, so it's not blocking, but the log volume buries real issues and I've observed a few grabs fail to reach RD during the loudest periods.

Can share diagnostic logs if useful.

[OnlyGoodGit]

Still running into this issue. No solution was provided, not sure why it was closed. Running version 2.0.130.0

Also, here's my usage so it's an API call issue and not a download limit issue.

[SquadCraftFTW]

not sure why it was closed

[dhuesca]

I'm having the same issue.
The error message says infringing file, but when I got to real-debrid website I can download the file just fine.

[KRiZ-R]

Same issue here!

[SquadCraftFTW]

I'm having the same issue.
The error message says infringing file, but when I got to real-debrid website I can download the file just fine.

Check this, I've been having issues accessing via API on gelato and stremio as well, seems to be a rdt issue. Moving to torbox fixed the issue for me, RD gave me a 9.3 euro refund for the remaining 12 euros left of my 180 days plan after politely asking support which was quick and easy.
https://www.reddit.com/r/debridmediamanager/comments/1t9l96i/realdebrids_infringing_file_errors_are/

Edit: also haven't noticed API errors yet

[TheTechRun]

I'm having the same issue.
The error message says infringing file, but when I got to real-debrid website I can download the file just fine.

Check this, I've been having issues accessing via API on gelato and stremio as well, seems to be a rdt issue. Moving to torbox fixed the issue for me, RD gave me a 9.3 euro refund for the remaining 12 euros left of my 180 days plan after politely asking support which was quick and easy. https://www.reddit.com/r/debridmediamanager/comments/1t9l96i/realdebrids_infringing_file_errors_are/

Edit: also haven't noticed API errors yet

It’s not an RD or Torbox issue. It’s an RDT issue. My RD account was banned a day or two before my first comment on here. I was using RD with RDT for about 4-5 years with no issue, so I'm pretty sure it was this rate limit bug that did it. I switched to torbox and had the same exact issue. Which confirmed my suspicions even more. That’s when I switched to decypharr and no rate limits. I have both RDT and decypharr as downloaders for sonar and radarr. That way I can easily check/uncheck “enable” … to enable the working one and disable the other one that is acting up.
It seems like the developer has no plan on fixing this, or maybe he’s just busy. Who knows.