Stuck at searching

[aldarund]

Cliflix ask what to watch. I enter something. Then nothing happens, it just stuck doing nothing ( or displaying nothing) forever ( or at least hour).
https://i.imgur.com/AnRKQwy.png
is there any debug mode or logs to pinpoint the problem?

[fabiospampinato]

I assume you're running on the latest version, is that correct?

The way that cliflix works in that situation is this:

• It searches the first active torrents provider
• If no torrents are found it tells you so
• Then it searches the next torrents provider
• And so on...
• If there are no more torrents providers to try and still no torrents have been found it will ask you to write another query

Have you tried executing cliflix again? Is the problem still happening?

Have you tried setting a different default active provider?

[aldarund]

Ye, im on latest. Yes, the problem persist no matter what i search. Tried several times.
Didnt tried to set different provider, all default.
Where would be ~/.cliflix.json located on win sybsystem?

[fabiospampinato]

Ye, im on latest. Yes, the problem persist no matter what i search. Tried several times.

This is pretty weird 🤔 There's no "debugging mode" other than actually debugging the program.

Where would be ~/.cliflix.json located on win sybsystem?

I don't know, I'm not familiar with Windows, maybe C:\Users\your-username? If you have an half-decent shell installed on your system you can check this with cd ~ && pwd.

[aldarund]

Ye, found. Tried to set different torrent providers as active - no luck, still same stuck behavior. And i dont even see any network activity from node process at all when its stuck. It do some initial package exachange and than nothing happens

[fabiospampinato]

🤔 weird, unfortunately I can't reproduce the problem so I can't work on a fix. If you'd like to investigate this yourself you should maybe put a few console.log calls here and there to see where the code halts, or even better attach a debugger to the app.

[kalkun]

This happens to me when searching with a danish IP where most sites are blocked.

[pysiak]

So it halts on
const torrents = await torrentSearch.search ( query, category, rows );
It doesn't go past that, but what's weird is that if you use lucky guess, it works!
Lucky is rows = 1 so I tried hardcoding rows to 1 to if this is it, but it's something else.

I'm very new to typescript and node so sorry if this is not too much, but it's as far as I was able to get in about 1h from zero :-)
Does that help?

[fabiospampinato]

For those who are experiencing this problem you might want to remove a default torrent provider by unsetting the torrens.providers.active setting. Or you could try setting a different default provider.

[Rickard-Martensson]

What bothers me is that it works when you do the "im feeling lucky".

cliflix The Great Dictator

always works fine, while

cliflix
The Great Dictator

always gets stuck on the first provider

What is the code doing when it says "waiting for %torrentprovider%"?
It keeps waiting for "Rarbg"... for example even though Rarbg very clearly have the torrent im looking for.

[hp4k1h5]

I've seen this behavior also on public networks like cafe hotspots. It's likely that torrent domains are being blocked or routed to a bad address, causing an indefinite hang. The "lucky" option returns a result, but i dont think i was ever able to download when the search was blocked.
my pr doesn't address the network layer block, but does provide a limit of 30 seconds to any search query