Hi! I'm on SparkBox 1.6.155 and trying to get 1337x working with FlareSolverr. Here's my current setup: FlareSolverr is running and healthy Manually added FlareSolverr as a proxy in Prowlarr at http://localhost:8191/ Added flaresolverr tag to the FlareSolverr proxy AND to the 1337x indexer Tested all base URLs: ❌ https://1337x.to/ - failed to connect ❌ https://1337x.st/ - failed to connect ✅ https://x1337x.ws/ - only one that worked ❌ https://x1337x.eu/ - didn't try Manual test passes ✅ but after saving I get "Unable to connect to indexer, Http request timed out" 1337x shows a warning triangle in the indexer list Also noticed my server did a rollback at 12:03 AM today - not sure if related Questions: Is my manual FlareSolverr/Prowlarr setup correct for 1.6.155? Is there a built-in FlareSolverr opt-in profile I'm missing? Could the rollback be causing issues? Thanks!
4 replies
tomspark wrote:
Good news — your setup is correct for 1.6.155. On SparkBox, Prowlarr and FlareSolverr both run inside the VPN's network namespace, so http://localhost:8191/ IS the right host — you didn't do anything wrong there. Your 2nd question: SparkBox auto-registers FlareSolverr in Prowlarr already, so you've probably got two proxy entries now (yours + the built-in one). Harmless — you can delete the manual one and keep the built-in. The flaresolverr tag on both the proxy and the indexer is exactly right. The timeout is almost certainly 1337x, not SparkBox. Their domains are heavily Cloudflare-gated and most mirrors are dead right now — you found x1337x.ws is the only one connecting, so set that as the indexer's base URL and drop the others. 'Manual test passes but sync times out' usually just means the live query is slower than the quick test through the bypass; bump the FlareSolverr proxy's request timeout from 60s to ~120s and re-test. The 12:03 AM rollback is the nightly auto-update playing it safe — it tried an update, something hiccuped, and it rolled you back to a known-good state. You're still on 1.6.155, so it's not what's affecting the indexer. If it rolls back every night, tell me and I'll dig into that separately.
kaizenbox wrote:
Hey Tom! (This is Kaizurea - I lost access to my old account because NordPass didn't save my password and I have no email recovery. Is there any way to transfer my license key from my old account to this one?) Anyway I have an issue with my SparkBox setup: What We Set Up: We successfully created two rdt-client containers: rdt-client (port 6500) for Real-Debrid rdt-client-torbox (port 6501) for TorBox Both containers are running and downloading successfully! The Actual Problem: The end goal is for Sonarr and Radarr to automatically pick up and import downloads from Real-Debrid and TorBox. But rdt-client saves files to /data/torrents which Sonarr and Radarr cannot see - they only have access to /opt/sparkbox/data/media. So files download successfully but never get imported! What We Tried: We added /data/torrents:/data/torrents as a volume mount to both Sonarr and Radarr in /opt/sparkbox/modules/media/docker-compose.yml but when recreating the containers we get: failed to create network mediasbmedia: Pool overlaps with other one on this address space Now Sonarr and Radarr are completely offline! Thanks!
tomspark wrote:
Let's get Sonarr and Radarr back online first. That "Pool overlaps with other one on this address space" error is a Docker network clash between your custom rdt-client containers and SparkBox's media network. Heads-up: SparkBox manages that media compose file and resets it on every update, so hand-edits there won't stick — put it back to stock and run sudo sparkbox up. If it still complains about that network, reply back and I'll help you clear the leftover one. To get your Real-Debrid/TorBox downloads seen by Sonarr/Radarr without editing compose at all: point rdt-client to save inside your media folder (e.g. /opt/sparkbox/data/media/torrents). Sonarr and Radarr already see that whole folder as /data, so they'll pick the downloads up automatically, and it survives updates. (rdt-client isn't a built-in module, so that part's custom territory — but this should unblock you.) On the lost account and license — totally fixable, sit tight and I'll get it sorted.
Chris wrote:
Coming back to this one because you were told to sit tight, and then nobody came back to you. That is two months, and I am sorry — the licence half of your question got lost behind the Sonarr fix. Recovering an account and moving a key across to a new one is not something I can do from support. That one is Tom's call and he handles these himself, so I have flagged your thread straight to him with both usernames noted. One thing while you wait: please do not post your licence key or account details here. This is a public thread, and he will not need them posted to find you. — Chris