Interactive search needs more time for this provider

[languagemaniac]

Interactive search needs more time for this provider

[mynameisbogdan]

The default timeout is 100 seconds per HTTP request, so there's plenty of time.

Due to lack of trace logs and no plans to change this default timeout, I'm going to close this.

[languagemaniac]

You need to check the trace logs and see what requests Radarr is making to Jackett for and if those links even return something by using something like curl or postman.

It's like as soon as it detects some torrents just cuts the search

It doesn't work like that, it waits for every indexer to finish before returning all the releases. Did you tried disabling 1337x and did a search to prove your assumption?

Ok you're right, I was wrong with my assumption. If I disable 1337x it won't return any result so I'll check more logs and see if I can find the culprit

[languagemaniac]

100 seconds per HTTP request, so there's plenty of time.

Due to lack of trace logs and no plans to change this default timeout, I'm going to close this

Can I manually change the http request timeout? Anyways it doesn't take that much as 100 seconds to show results in jacket, it could be something else? I could time it. It also doesn't take as much as 100 seconds to show results from 1337x. So I think it should wait until it gets results from the two providers.

The way it's working right now it just returns a bunch of results from 1337x. It's like as soon as it detects some torrents just cuts the search

[bakerboy448]

Can I manually change the http request timeout?

no and no plans to do so.

Again, given the invalid bug report and absence of the required trace logs there is no action to take here. Please visit discord for support questions.

[mynameisbogdan]

You need to check the trace logs and see what requests Radarr is making to Jackett for and if those links even return something by using something like curl or postman.

It's like as soon as it detects some torrents just cuts the search

It doesn't work like that, it waits for every indexer to finish before returning all the releases. Did you tried disabling 1337x and did a search to prove your assumption?

[languagemaniac]

You need to check the trace logs and see what requests Radarr is making to Jackett for and if those links even return something by using something like curl or postman.

It's like as soon as it detects some torrents just cuts the search

It doesn't work like that, it waits for every indexer to finish before returning all the releases. Did you tried disabling 1337x and did a search to prove your assumption?

I ran a query test with curl, should I open a new issue? The query test is ok, it returns results without any issues.

[mynameisbogdan]

Join our discord and ask in #radarr for support to troubleshoot if you can't follow the troubleshoot guide.

[languagemaniac]

Join our discord and ask in #radarr for support to troubleshoot if you can't follow the troubleshoot guide.

sorry I didn't know there was a troubleshoot guide. I will join discord. Apologies