-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
303 HTTP response #20
Comments
Thanks for the logs, I'll take a look and see if I can spot the issue. Out of curiosity is there anything interesting when you go to http://192.168.1.2:8989/api/v3/rootFolder in a browser? Also could you let me know what version of Sonarr you're using? |
hi, http://192.168.1.2:8989/sonarr/api/v3/rootFolder gives:
From the api docs:
gives:
sonarr version:
tested on windows aswell, same error |
is my docker run on unraid |
from sonarr logs. Ive setup overseerr today with the same api keys and ips, thats working fine |
Thanks for these. I will review the logs and see if I'm missing a use case, are you using login authentication on Sonarr? Also unrelated, but could you use the |
yeh i was just testing with alpha, ill swap back. no authentication: https://share.richowen.me/JOwa3/VAmedape64.png/raw |
ok its something to do with my URLBASE in sonarr/radarr, removed the /sonarr in the sonarr general and its connected, but i kinda need the url base lol |
Interesting, I'll replicate your setup (tomorrow) with the URLbase behind a reverse proxy and see if I can get the same error. Thanks for all the help debugging! |
thanks, glhf :D |
bit more info, changed to subdomains, connects ok but then throws:
|
tried with and without sonarr auth |
|
Thanks, I've raised a new issue for the Language profile error here, I'll fix both issues separately |
Regarding this issue, I was able to replicate it by setting my URLBase to
I think the fix would be to allow the user to define a baseurl via the environment variable: I'll fix that up now. Thanks for spotting this and all your debug logs! Made my life so much easier |
Hi, im on unraid, getting this error after community applications setup, changing sonarr and watchlist to matching networks doesnt help.
Exception in thread "main" java.lang.IllegalArgumentException: Unable to connect to Sonarr at http://192.168.1.2:8989, with error org.http4s.client.UnexpectedStatus: unexpected HTTP status: 303 See Other for request GET http://192.168.1.2:8989/api/v3/rootFolder
at configuration.Configuration.throwError(Configuration.scala:146)
at configuration.Configuration.$anonfun$getSonarrConfig$4(Configuration.scala:41)
at >>$extension @ org.typelevel.keypool.KeyPool$Builder.keepRunning$1(KeyPool.scala:370)
at >>$extension @ org.typelevel.keypool.KeyPool$Builder.keepRunning$1(KeyPool.scala:370)
at void @ org.typelevel.keypool.KeyPool$.reap(KeyPool.scala:187)
at unsafeRunSync @ configuration.Configuration.(Configuration.scala:19)
at getAndSet @ org.typelevel.keypool.KeyPool$.destroy(KeyPool.scala:120)
at >>$extension @ org.typelevel.keypool.KeyPool$Builder.keepRunning$1(KeyPool.scala:370)
17:31:51.137 [io-compute-15] ERROR configuration.Configuration - Unable to connect to Sonarr at http://192.168.1.2:8989, with error org.http4s.client.UnexpectedStatus: unexpected HTTP status: 303 See Other for request GET http://192.168.1.2:8989/api/v3/rootFolder
The text was updated successfully, but these errors were encountered: