New version no longer returning results #108
Comments
|
I have the same issue on an fresh docker install on unRAID. |
|
Same issue with fresh docker install on unRaid and fresh bot creation in Discord developer portal |
|
Did you guys try the image from @kiranshila himself? |
|
The unRaid docker template overview references this GitHub repository... (the one the issue is open on) But then the template points to the lsio repository, so unRaid is pulling it down from: Perhaps this issue should be moved to But if the logs also indicate kiranshila as the dev... Then perhaps @kiranshila can assist with getting the proper updates committed to the linuxserver repository? Also just attempted to pull the container down using |
|
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? |
|
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. |
|
Perhaps unraid changed how networking worked. Hmm.. |
|
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'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. |
LinuxServer wasn't working for me so I tried it directly using this image and it worked great. Just wanted to echo my +1 👍🏻 |
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! |
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. |
Describe the bug
Bot is not able to search for any content, responds with "No results found"
Expected behavior
Any search results are produced
Screenshots
Logs
Please copy out the log in it's entirety, please make sure to hide any potential secrets/API keys - although they should be censored via the logging program.
Additional context
This is running in a personal discord where the bot has admin perms and I am the Admin. The container is running in Unraid on the latest version.
The text was updated successfully, but these errors were encountered: