The internet is full of conflicting information, so I'll start by asking "Does FlareSolverr still work"? I know it can't solve CAPTCHAs anymore, but does it still work for regular CloudFlare protection?

Assuming it does, here's my issue:

Running FlareSolverr v3.3.25 on Windows 11 with Jackett v0.22.2052.

Run FlareSolverr as Admin. Sometimes it throws up a bunch of failures and crashes. Other times, it says "Serving on http://0.0.0.0:8191".

Run a test on Jacket on a popular public indexer (1337x). Once in a while, randomly, the test is successful. Usually, I get this error:

An error occurred while testing this indexer
Exception (1337x): Challenge detected but FlareSolverr is not configured: Challenge detected but FlareSolverr is not configured

So I'm thinking that Jackett can't "see" FlareSolverr, and I look at the configuration options. Notice "FlareSolverr API URL" is left blank for default. Look up the default URL and apparently it's 127.0.0.0:8191. Change the Jackett URL to "http://0.0.0.0:8191" and run another test. I get this error:

An error occurred while testing this indexer
Exception (1337x): Error connecting to FlareSolverr server: System.Net.Http.HttpRequestException: IPv4 address 0.0.0.0 and IPv6 address ::0 are unspecified addresses that cannot be used as a target address. (Parameter 'hostName') (0.0.0.0:8191) ---> System.ArgumentException: IPv4 address 0.0.0.0 and IPv6 address ::0 are unspecified addresses that cannot be used as a target address. (Parameter 'hostName') at System.Net.Dns.GetHostEntryOrAddressesCoreAsync(String hostName, Boolean justReturnParsedIp, Boolean throwOnIIPAny, Boolean justAddresses, AddressFamily family, CancellationToken cancellationToken) at System.Net.Sockets.Socket.ConnectAsync(SocketAsyncEventArgs e, Boolean userSocket, Boolean saeaCancelable) at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ConnectAsync(Socket socket) at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken) --- End of inner exception stack trace --- at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.AddHttp11ConnectionAsync(QueueItem queueItem) at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellat

What is going on and is there any way to make this work?