mirror of
https://github.com/Prowlarr/Prowlarr.git
synced 2026-03-02 22:57:22 -05:00
Sporadic issues with Toloka.to indexer when requesting a torrent file download #1245
Labels
No labels
Area: API
Area: Database
Area: Db-migration
Area: Download Clients
Area: Indexer
Area: Metadata API
Area: Notifications
Area: Tooling
Area: UI
Area: Update API
Priority: High
Priority: Low
Priority: Medium
Status: Cannot Reproduce
Status: Confirmed
Status: Help Wanted
Status: In Progress
Status: Indexer - need invite
Status: Info Needed
Status: Investigating
Status: Logs Needed
Status: Maybe One Day
Status: Needs Triage
Status: Unlikely
Status: Waiting for OP
Status: Won't Fix
Type: Bug
Type: Bug
Type: Documentation
Type: Duplicate
Type: Enhancement
Type: External Bug
Type: Feature Request
Type: Regression
Type: Support
Type: Support.
lidarr-pull
radarr-pull
sonarr upstream
sonarr-pull
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Prowlarr#1245
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @drrako on GitHub (Nov 8, 2025).
I attest that there is not an existing issue for this?
I attest this is not related to a Cardigann YML Indexer.
Current Behavior
When using the
Toloka.toindexer in Radarr/Sonarr, I frequently encounter the following problem:Based on the logs, it appears that grabbing the feed in problematic scenario is successful. However, when the client requests an actual torrent file,
toloka.toauthentication does not work and instead of providing the actual torrent file, it returns a login form page.Expected Behavior
The
Toloka.toindexer should consistently allow grabbing releases without requiring manual intervention in the System/Health section.Steps To Reproduce
Since issue is sporadic and most likely related to authentication flow/state - it is not very trivial to reproduce intentionally.
Environment
What branch are you running?
Master
Trace Logs?
toloka.to.report.log
prowlarr.debug.txt
I attest that Trace Logs have been provided as applicable. Reports will be closed if the required logs are not provided.
trace- that are relevant and show this issue.@mynameisbogdan commented on GitHub (Nov 8, 2025):
The debug logs aren't very useful.
But I noticed your download links contain a
&sid=somevaluewhile I'm not getting anysidquery params. Did you enabled some option on their site that might affect this?@drrako commented on GitHub (Nov 8, 2025):
Here are the profile settings I have:
I will also enable trace level logging moving forward, as it may provide more helpful information.
Interestingly, on the second (successful) attempt - after I fixed the indexer in System/Health - the
&sid=somevalueparameter was no longer present in the query (you can see this in the logs I attached). I also tested the link with the&sid=somevalueparameter in an authenticated Firefox tab, and it worked fine for me.@drrako commented on GitHub (Nov 8, 2025):
Here is the trace log that captures the exact same steps:
System/Healthpage.prowlarr.trace.txt