New version no longer returning results about doplarr HOT 13 OPEN

Did you guys try the image from @kiranshila himself? ghcr.io/kiranshila/doplarr:latest
I just deployed this in a docker stack with no issues.

from doplarr.

Here is my log, using lsio repository... starts up fine and connects to Discord successfully but then has this FATAL error when I did a test search for 2 Fast 2 Furious.

from doplarr.

Here is my log, using lsio repository... starts up fine and connects to Discord successfully but then has this FATAL error when I did a test search for 2 Fast 2 Furious.

This error message was caused by using localhost instead of the actual ip address of the doplarr/radarr server for me.

I was already referencing localhost, but you got me thinking about network config... thank you!

My Radarr and Sonarr instances (unRaid docker) are routed through another (a VPN container), once I routed the Doplarr container through that same VPN container everything works as expected!

from doplarr.

I have the same issue on an fresh docker install on unRAID.

from doplarr.

Same issue with fresh docker install on unRaid and fresh bot creation in Discord developer portal

from doplarr.

The unRaid docker template overview references this GitHub repository... (the one the issue is open on)
*Doplarr(https://github.com/kiranshila/Doplarr) is an arr request bot for Discord."

But then the template points to the lsio repository, so unRaid is pulling it down from:
lscr.io/linuxserver/doplarr

Perhaps this issue should be moved to
https://github.com/linuxserver/docker-doplarr ?

But if the logs also indicate kiranshila as the dev...
To support the app dev(s) visit:
kiranshila: https://github.com/sponsors/kiranshila

Then perhaps @kiranshila can assist with getting the proper updates committed to the linuxserver repository?

Also just attempted to pull the container down using
ghcr.io/kiranshila/doplarr:latest (by changing reference in unRaid repository template) and get same result (Search result returned no hits).

from doplarr.

Theoretically the lsio (and other repackagers) docker containers use the same JAR used in my image - so I'm not quite sure why it would differ in behavior. Is everyone getting this error using Unraid? Is everyone getting that same SSL error?

from doplarr.

Perhaps unraid changed how networking worked. Hmm..

from doplarr.

I'm on unRaid 6.11.5, using the default Network Type of Bridge (default in the template)

The template also has the two OVERSEERR (API & URL) keys as required fields yet instructs them to be left blank when using Radarr/Sonarr... let me know if you'd like me to spin up an issue over on Lsio's GitHub for those separately.
I edited them to not be required and leaving them blank causes fatal errors as the code is expecting values in the environment variables... so a faux API key has been entered.

from doplarr.

I'm getting the exact same error, happens both when using the LSIO container on unraid along side overseerr, radarr, & sonarr. As well as when running on my dedicated and higher performance docker vm (on proxmox on another host).

Of note, the LSIO on unraid option worked once but gave me some 'close but not quite what I wanted' results. When I tested directly in overseerr and sonarr and got the expected results I went back to discord and re-tested and it never worked again.

from doplarr.

Did you guys try the image from @kiranshila himself? ghcr.io/kiranshila/doplarr:latest I just deployed this in a docker stack with no issues.

LinuxServer wasn't working for me so I tried it directly using this image and it worked great. Just wanted to echo my +1 👍🏻

from doplarr.

Here is my log, using lsio repository... starts up fine and connects to Discord successfully but then has this FATAL error when I did a test search for 2 Fast 2 Furious.

This error message was caused by using localhost instead of the actual ip address of the doplarr/radarr server for me.

from doplarr.

2023-03-21T17:08:27.754Z e9eba51c766e INFO [doplarr.interaction-state-machine:28] - Performing search for series House
2023-03-21T17:08:27.759Z e9eba51c766e FATAL [doplarr.utils:78] -
java.lang.Thread.run
java.util.concurrent.ThreadPoolExecutor$Worker.run
java.util.concurrent.ThreadPoolExecutor.runWorker
java.util.concurrent.CompletableFuture$AsyncSupply.run
java.util.concurrent.CompletableFuture.postComplete
java.util.concurrent.CompletableFuture$UniHandle.tryFire
java.util.concurrent.CompletableFuture.uniHandle
jdk.internal.net.http.PlainHttpConnection.lambda$connectAsync$1
jdk.internal.net.http.PlainHttpConnection.checkRetryConnect
jdk.internal.net.http.PlainHttpConnection.connectAsync
java.security.AccessController.doPrivileged
jdk.internal.net.http.PlainHttpConnection.lambda$connectAsync$0
sun.nio.ch.SocketChannelImpl.connect
sun.nio.ch.SocketChannelImpl.beginConnect
sun.nio.ch.SocketChannelImpl.ensureOpen
java.nio.channels.ClosedChannelException:
java.net.ConnectException:
java.util.concurrent.CompletionException: java.net.ConnectException

Same issue still using the latest. Both LSIO and ghcr.io/kiranshila/doplarr:latest on unRaid. Sonarr/Radarr/Doplarr are all in Docker on the same network.

Edit: So, I figured out what was causing it for me. The LSIO adds the overseer variables and requires them. Even if you set them to not required and leave them blank as suggested it errors and the container stops. If you switch to ghcr.io/kiranshila/doplarr:latest and remove both overseer (if you're not using it) variables it will stop trying to default to it and will instead use Sonarr.

In short it seems the error is that it's actually defaulting to overrseer if the variables exist at all, which the LSIO image requires - for me at least.

from doplarr.