mirror of
https://github.com/Prowlarr/Prowlarr.git
synced 2026-03-02 22:57:22 -05:00
M-Team redirected to Google #898
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#898
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 @Gladtbam on GitHub (Jul 11, 2023).
Is there an existing issue for this?
Current Behavior
M-Team has not been working properly for almost a month, I added it again and it shows redirected to google.com
Unable to connect to indexer. Redirected to https://www.google.com/torrents.php?cat401=1&cat419=1&cat420=1&cat421=1&cat439=1&cat403=1&cat402=1&cat435=1&cat438=1&cat404=1&cat405=1&cat407=1&cat422=1&cat423=1&cat427=1&cat409=1&search=&incldead=0&spstate=0&search_area=0&search_mode=0&sort=4&type=desc¬newword=1 from indexer requestExpected Behavior
should redirect correctly
Steps To Reproduce
Environment
What branch are you running?
Master
Trace Logs?
Flaresolverr Docker logs did not add m-team's log
Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided.
trace- that are relevant and show this issue.@bakerboy448 commented on GitHub (Jul 11, 2023):
Duplicate of https://github.com/Prowlarr/Prowlarr/issues/1061
relating to https://github.com/Prowlarr/Prowlarr/issues/1307
not a Prowlarr issue. M-team dislikes automation and actively tries to break it
please search next time as the template indicates
for future reference the provided logs are also invalid for bug reports and are not the required trace logs with context the template asks for; Flaresolverr logs has no relevance to Prowlarr
@Gladtbam commented on GitHub (Jul 12, 2023):
On the same server as prowlarr, I successfully added the M-Team using Jackett and the search is also available
I recrawled a trace log
prowlarr.debug.txt
prowlarr.trace.txt
@ohsc commented on GitHub (Aug 10, 2023):
I have the same issue. I noticed that Prowlarr doesn't invoke Flaresolverr after matching the tag. Flaresolverr doesn't have any invocation logs. However, everything works fine when I switch to Jackett, and Flaresolverr has invocation logs.
prowlarr.trace.txt
prowlarr.debug.txt
@bakerboy448 commented on GitHub (Aug 10, 2023):
Please do not spam closed duplicate issues.
this is a tracker problem that has no resolution for prowlarr - they hate automation