Failed to test proxy #1114
-
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 |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 17 replies
-
What are you using for FlareSolverr's API URL in Prowlarr? Are you using a proxy or VPN? |
Beta Was this translation helpful? Give feedback.
Looking a little closer at your compose, the hostname for the FlareSolverr container is actually
7cf070e5f81c
rather thanflaresolverr
, so you can tryhttp://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 thetrash-guides_default
network, so I'm going to guess that's why they can't communicate.