Skip to content
Discussion options

You must be logged in to vote

The download fetch blocks loopback on purpose: the .torrent/.nzb URL comes from the indexer's response, not from your config, so a compromised indexer could otherwise aim it at a service bound to Bindery's own 127.0.0.1. Your Prowlarr base URL is fine on loopback (and search already reaches it that way), but the download link it hands back is what gets rejected.

Two ways forward:

1. Works on current Bindery. Point Bindery at Prowlarr by a non-loopback address so the links it returns land in RFC1918, which is allowed. Use the host LAN IP, the Docker bridge gateway (172.17.0.1 / host.docker.internal), or the compose service name (e.g. http://prowlarr:9696). This only falls short if Bindery …

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by vavallee
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants