Unable to connect to indexer. This is typically caused by DNS/SSL issues. Check DNS settings, ensure IPv6 is working or disabled, consider using different DNS servers, or try a VPN/proxy if needed. See: 'https://wiki.servarr.com/prowlarr/troubleshootingdns-ssl-connection-issues' The response ended prematurely while waiting for the next frame from the server. (ResponseEnded) getting this error when trying to add certain indexers on prowlerr... not sure whats going on.
9 replies
tomspark wrote:
You didn't break anything — since it's only certain indexers, your setup is working and those specific sites are the fussy ones. The usual cause: some indexer sites put up an 'are you a robot?' check that blocks apps like Prowlarr, and that check is what cuts the connection off early with that exact error. SparkBox ships a helper for this, already wired in. Edit the failing indexer in Prowlarr, scroll down to the Tags box, type flaresolverr and press Enter, then Save and hit Test again — it should go green. If one still fails after the tag, reply with which indexers are acting up and I'll dig into those specifically.
Grimma84 wrote:
1337x, and eztv still having the issue.
tomspark wrote:
Thanks for checking — those two use a newer, tougher robot-check that the standard helper can't get past, but SparkBox ships a stronger one called Byparr for exactly this. In your dashboard, open the Media module's settings and flip on 'Use Byparr instead of FlareSolverr', then save. Give it a minute to swap over, then hit Test on 1337x and eztv in Prowlarr again — keep the flaresolverr tag on them, nothing else changes. If either still fails after that, paste the new error here and I'll dig into it.
Grimma84 wrote:
Unable to connect to indexer. Unexpected response status Forbidden code from indexer request, and this Unable to connect to indexer, indexer's server is unavailable. Try again later. HTTP request failed: [500:InternalServerError] [POST] at [http://localhost:8191/v1] still getting these 2 errors, eztv is the second error.
tomspark wrote:
Thanks for the details. Those errors — especially the 500 from localhost:8191 — suggest Byparr might not be starting cleanly or timing out on those sites. Quick diagnostic: in your SparkBox dashboard, open Media settings and confirm 'Use Byparr instead of FlareSolverr' is toggled ON, then save. Wait 2 minutes for it to spin up. If Byparr isn't running or keeps restarting, that 500 error makes sense. If it is running, paste the full error when you hit Test on 1337x — that'll help us narrow down if it's a Byparr config issue or if those sites added another protection layer.
tomspark wrote:
Thanks for hanging in there — one quick check so we know exactly where this stands. On your box, run: sudo docker ps --format '{{.Names}}' That prints a short list of the apps that are running. Look for sb-byparr in that list. If it's there, the swap worked, and these two errors mean 1337x and eztv are blocking harder than usual right now — usually they're refusing the VPN's address itself, which no helper can talk around. That's their blocking, not your setup, and your other indexers aren't affected. Moving the VPN to a different city usually gets past it — happy to walk you through that next. If the list says sb-flaresolverr instead, tell me and we'll fix the toggle.
Grimma84 wrote:
sb-byparr is int hat list. whats the walkthrough to change the vpn city?
tomspark wrote:
Nice, that confirms everything on your end is set up right — those two sites are just refusing the address your VPN is using, and changing the city gets you a fresh one. It's on the same settings page as before: dashboard, Media module settings, find the box called VPN Server Cities. Type one big city from the country shown in VPN Server Country — if that says United States, try Chicago — then Save and give it a couple of minutes to reconnect. Then hit Test on 1337x and eztv in Prowlarr again. If they're still unhappy, swap the city for another one (Dallas, Seattle) and retest — sometimes it takes two or three tries to land on an address these sites accept.
Grimma84 wrote:
That Worked! sweet! thank you again!