Skip to content

Issue Report - ncore - Fix requested #692

@kriziw

Description

@kriziw

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Type {Torrent|Usenet}: Torrent
Tracker {Name}: Ncore
URL {URL}: ncore.pro

Additional Information:

The current implementation of the ncore indexer integration is using a pull of the /browse.php path and using CSS selectors to get the content. This is triggering a rate limiting on the ncore platform which results in the indexer becoming unavailble (429:TooManyRequests).

Expected Behavior

The recommended fix is to move to a JSON-pull via https://ncore.pro/torrents.php?jsons=true to overcome this.

Note: ncore support staff has been contacted - issue resolution is suggested by ncore technical team

Steps To Reproduce

No response

Environment

- OS: Debian 13
- Prowlarr: Latest
- Docker Install: Yes
- Using Reverse Proxy: only for local access
- Browser: Chrome

What branch are you running?

Master

Trace Logs? Not Optional

prowlarr.txt

prowlarr.debug.txt

Trace Logs have been provided as applicable. Reports will be closed if the required logs are not provided.

  • I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain trace - that are relevant and show this issue.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions