Failed to test proxy

[1ReallyLongName]

Hello, I created the FlareSolverr container using docker-compose and I am able to access the website manually; however, it will not be found within Prowlarr. This is my first GitHub discussion, so please let me know if I broke any best practices, or if I can provide you anything else.

When I manually go to the address I see this: {"msg": "FlareSolverr is ready!", "version": "3.3.16", "userAgent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36"}

docker-compose: https://privatebin.net/?4e48eb83c697af6e#CPAg5vrUf8GZtKCPeu5JrjkkvHqX8URSJU2hqz1NEa6E

QNAP NAS TVS-682: Firmware version: QTS 5.1.5.2679
Prowlarr version: 1.13.3.4273
FlareSolver version: 3.3.16

[ilike2burnthing]

What are you using for FlareSolverr's API URL in Prowlarr?

Are you using a proxy or VPN?

[1ReallyLongName]

I was wondering. Sadly the exact same result.

[ilike2burnthing]

Are you currently running Prowlarr and FlareSolverr as Docker swarm? If so, just set them up as two separate containers and see if that makes a difference.

[1ReallyLongName]

I'm not even too sure what a docker swarm is so I'm going to bet I do not have it set up as a swarm 😅

Looking in my container station they are separate containers though, and I have them separated in my docker compose.

[ilike2burnthing]

Looking a little closer at your compose, the hostname for the FlareSolverr container is actually 7cf070e5f81c rather than flaresolverr, so you can try http://7cf070e5f81c:8191 (in Prowlarr, and if that doesn't work then with curl).

---

I've typed that and then read further. You have Prowlarr on the media_default network and FlareSolverr on the trash-guides_default network, so I'm going to guess that's why they can't communicate.

[1ReallyLongName]

I see that now and believe you're absolutely right. I'm super new to docker-compose so I'm very confused because I never designated each of them different networks. Also, I'm assuming it's because I made edits to my original docker compose, but now it won't let me close any of my previous ones containers through docker compose down. Just this new one.

[1ReallyLongName]

You were absolutely right! It seems way too obvious now. For some reason it created two separate ones when I installed flaresolverr separately. So I had to remove all of them through container station and then rerun docker compose. Thank you for all your help and sorry for the goose chase!