Closed blueyoshi2015 closed 2 years ago
Make sure you're running the latest Unpackrr and the latest Radarr (4.x) and Sonarr (3.x), recent changes to all three have caused compatibility issues. I just ran into this with Sonarr because I was still on 2.x.
Fwiw Sonarr v2 has not been supported for over a year since v3 dropped
Make sure you're running the latest Unpackrr and the latest Radarr (4.x) and Sonarr (3.x), recent changes to all three have caused compatibility issues. I just ran into this with Sonarr because I was still on 2.x.
I’m on version 4 of Radarr and 3 for Sonarr.
Fwiw Sonarr v2 has not been supported for over a year since v3 dropped
Yeah I’m up to date on Sonarr and Radarr.
The main error code is:
2022/04/02 05:00:53.389885 radarr.go:110: [ERROR] Radarr (http://192.168.1.9:7878): api.Get(queue): failed: (status: 302 Found): invalid status code, <200||>299: 2022/04/02 05:00:53.390806 sonarr.go:109: [ERROR] Sonarr (http://192.168.1.8:8989): api.Get(queue): failed: (status: 303 See Other): invalid status code, <200||>299:
It's not real clear what we're trying to fix here. In the logs above you changed the sonarr and radarr URLs at least 3, maybe 4 times. Looks like you got it right on the last try as those logs look good, and no longer use the URL you put in your original message as "the main error code is."
But you did mention:
THAT works. Until it doesn't.
so.... what happens when "it doesn't" ? Because right now it is. I'd suggest adding a delay to your unpackerr startup, so it starts after sonarr and radarr. If it starts first, it wont be able to use Docker's DNS to resolve their container names.
Please show me the errors you get while in this current configuration.
The main error code is:
2022/04/02 05:00:53.389885 radarr.go:110: [ERROR] Radarr (http://192.168.1.9:7878): api.Get(queue): failed: (status: 302 Found): invalid status code, <200||>299: 2022/04/02 05:00:53.390806 sonarr.go:109: [ERROR] Sonarr (http://192.168.1.8:8989): api.Get(queue): failed: (status: 303 See Other): invalid status code, <200||>299:
It's not real clear what we're trying to fix here. In the logs above you changed the sonarr and radarr URLs at least 3, maybe 4 times. Looks like you got it right on the last try as those logs look good, and no longer use the URL you put in your original message as "the main error code is."
But you did mention:
THAT works. Until it doesn't.
so.... what happens when "it doesn't" ? Because right now it is. I'd suggest adding a delay to your unpackerr startup, so it starts after sonarr and radarr. If it starts first, it wont be able to use Docker's DNS to resolve their container names.
Please show me the errors you get while in this current configuration.
I think the delay is the key here. I’ll try that and see if the issue crops up again. I’ll close the issue for now, and if I get another problem in the current configuration and the delay I’ll open a new one. Thanks!
Sounds good. You can always rile me up on Discord a bit faster if you have more errors crop up. 🤞
I'm experiencing an issue where Unpackerr will not connect to the other arr clients. I've been unable to determine why this happens. I've tried assigning the arr containers static IP addresses and updating that in the .conf file. After I restart Unpackerr, that works.... until it doesn't. I confirm that the *arr containers have not changed their IP addresses and that the .conf file is correct. I then change the .conf file to use the container names, since all my dockers are on the same network. Restart Unpackerr, and THAT works. Until it doesn't. So I'm stuck in this cycle of having to go back and forth every time a download doesn't get unpacked. I'm including my logs below. I tried a few other configurations of IP address/port formatting, but those (obviously) didn't work at all.
The main error code is:
Thanks for any help!