ZonaQ indexer is not working #1263

Open
opened 2026-02-20 10:09:05 -05:00 by deekerman · 3 comments
Owner

Originally created by @ngosang on GitHub (Dec 12, 2025).

I attest that there is not an existing issue for this?

  • I have searched the existing open and closed issues
  • I confirm this is not related to a Cardigann YML Indexer

Current Behavior

I can't login in ZonaQ. This indexer is working well in Jackett. It has been working for years.

Expected Behavior

Be able to configure ZonaQ indexer.

Steps To Reproduce

No response

Environment

- OS: Docker Linux
- Prowlarr: 2.3.0.5236
- Docker Install: Linuxserver
- Using Reverse Proxy: No
- Browser: Firefox

What branch are you running?

Master

Trace Logs?

trace_zonaq.txt

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

  • I attest that 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.
Originally created by @ngosang on GitHub (Dec 12, 2025). ### I attest that there is not an existing issue for this? - [x] I have searched the existing open and closed issues ### I attest this is not related to a Cardigann YML Indexer. - [x] I confirm this is not related to a Cardigann YML Indexer ### Current Behavior I can't login in ZonaQ. This indexer is working well in Jackett. It has been working for years. ### Expected Behavior Be able to configure ZonaQ indexer. ### Steps To Reproduce _No response_ ### Environment ```markdown - OS: Docker Linux - Prowlarr: 2.3.0.5236 - Docker Install: Linuxserver - Using Reverse Proxy: No - Browser: Firefox ``` ### What branch are you running? Master ### Trace Logs? [trace_zonaq.txt](https://github.com/user-attachments/files/24133334/trace_zonaq.txt) ### I attest that Trace Logs have been provided as applicable. Reports will be closed if the required logs are not provided. - [x] I attest that 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.
Author
Owner

@ilike2burnthing commented on GitHub (Dec 13, 2025):

UA starting Prowlarr is being blocked. You'd need to contact tracker staff to see if this was intentional (I don't have an account).

@ilike2burnthing commented on GitHub (Dec 13, 2025): UA starting `Prowlarr` is being blocked. You'd need to contact tracker staff to see if this was intentional (I don't have an account).
Author
Owner

@ngosang commented on GitHub (Dec 14, 2025):

WIP

@ngosang commented on GitHub (Dec 14, 2025): WIP
Author
Owner

@ngosang commented on GitHub (Dec 15, 2025):

I asked the site's staff, and they are against automated tools. They are not willing to unblock Prowlarr UA.

@ngosang commented on GitHub (Dec 15, 2025): I asked the site's staff, and they are against automated tools. They are not willing to unblock Prowlarr UA.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Prowlarr#1263
No description provided.