mirror of
https://github.com/Sonarr/Sonarr
synced 2024-12-23 00:07:07 +00:00
Add section on rate limits due to vpn/proxy.
parent
e18d96d67c
commit
d075c26ae8
1 changed files with 3 additions and 0 deletions
|
@ -50,6 +50,9 @@ Sometimes indexers will return completely unrelated results, Sonarr will feed in
|
||||||
### Certificate validation
|
### Certificate validation
|
||||||
You'll be connecting to most indexers/trackers via https, so you'll need that to work properly on your system. That means your time zone and time both need to be set *correctly*. It also means your system certificates need to be up to date. And if you're using Mono, `MONO_TLS_PROVIDER=legacy` was a fix from *years* ago that should *not* be used anymore, so make sure you're not setting that accidentally.
|
You'll be connecting to most indexers/trackers via https, so you'll need that to work properly on your system. That means your time zone and time both need to be set *correctly*. It also means your system certificates need to be up to date. And if you're using Mono, `MONO_TLS_PROVIDER=legacy` was a fix from *years* ago that should *not* be used anymore, so make sure you're not setting that accidentally.
|
||||||
|
|
||||||
|
### Hitting rate limits
|
||||||
|
If you run your Sonarr through a VPN or proxy, you may be competing with 10s or 100s or 1000s of other people all trying to use services like TVDB, Xem and/or your indexers and trackers. Rate limiting and ddos protection are often done by IP address and your VPN/proxy exit point is *one* IP address. Unless you're in a repressive country like China, Australia or South Africa you don't need to VPN/proxy your Sonarr/Radarr.
|
||||||
|
|
||||||
## Errors
|
## Errors
|
||||||
|
|
||||||
These are some of the common errors you may see when adding an indexer
|
These are some of the common errors you may see when adding an indexer
|
||||||
|
|
Loading…
Reference in a new issue