Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MirCrew-Releases Indexer fail #401

Closed
2 tasks done
IvanMazzoli opened this issue Jan 29, 2024 · 9 comments · Fixed by #402
Closed
2 tasks done

MirCrew-Releases Indexer fail #401

IvanMazzoli opened this issue Jan 29, 2024 · 9 comments · Fixed by #402
Labels
Status: Needs Triage Type: Bug Something isn't working with an indexer

Comments

@IvanMazzoli
Copy link

IvanMazzoli commented Jan 29, 2024

Is there an existing issue for this?

  • I have searched the existing open and closed issues

Current Behavior

The indexer fails when added to the indexers list. Worked fine since last week

Unable to connect to indexer, check the log above the ValidationFailure for more details. HTTP request failed: [403:Forbidden] [GET] at [https://mircrew-releases.org/ucp.php?mode=login]

Expected Behavior

When adding the indexer, with the correct username and password, it should work as intended.

Steps To Reproduce

  1. Add the Mircrew indexer to Prowlarr with a valid username and password
  2. Click the "Test" button

Environment

- OS: Ubuntu 23.04
- Prowlarr: 1.12.2.4211
- Docker Install: Yes
- Using Reverse Proxy: No

What branch are you running?

Master

Trace Logs?

prowlarr.trace.txt

Trace Logs have been provided as applicable. Reports may 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.
@IvanMazzoli IvanMazzoli added Status: Needs Triage Type: Bug Something isn't working with an indexer labels Jan 29, 2024
@mynameisbogdan mynameisbogdan transferred this issue from Prowlarr/Prowlarr Jan 29, 2024
@mynameisbogdan
Copy link
Contributor

<html>
<head><title>403 Forbidden</title></head>
<body bgcolor="white">
<center><h1>403 Forbidden</h1></center>
<hr><center>nginx</center>
</body>
</html>

Not a Prowlarr issue, either you're being blocked per IP or they blocked Prowlarr for everyone.

@pbarone
Copy link

pbarone commented Jan 29, 2024

Works on my machine with Jackett so it's not my IP (no VPN is used for either). Also, the same started happening at the same time with Il Corsaro Nero and Il Corsaro Blu... all worked before the latest update

logs.txt

@mynameisbogdan
Copy link
Contributor

@pbarone please restart Prowlarr and try again.

@pbarone
Copy link

pbarone commented Jan 29, 2024

I changed from "nightly" to "latest" docker tag and it seems to have fixed the issue

image: linuxserver/prowlarr:latest

@mynameisbogdan
Copy link
Contributor

Nop, it was fixed in #402.

@pbarone
Copy link

pbarone commented Jan 29, 2024

Well... Corsaro Nero, Corsaro Blu and MIRCrew were broken for me with Nightly (several restarts). Worked after I moved to Latest. If you want I can get Nightly again and see if the issue comes up again.

Currently on Package Version
1.12.2.4211-ls49 by linuxserver.io

@ilike2burnthing
Copy link
Contributor

Nero has been down for a week, and still is, so I don't see how it would be working for you now - Jackett/Jackett#986

@pbarone
Copy link

pbarone commented Jan 29, 2024

Odd, it had a green checkmark. Now it is back red but Blue and MIRCRew are green

@IvanMazzoli
Copy link
Author

Just tested Mircrew again, seems to be working fine without the need to restart the container or move to nightly builds. Seems to be an error on their side.
Nero seems to be offline, but this goes beyond the scope of this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Triage Type: Bug Something isn't working with an indexer
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants