Potential Bug: Can't update sonarr/radarr urls with categories in use when existing url is no longer reachable

[edrock200]

So, I think this is a bug but not sure. We moved some bots to another host. Prior they were local to sonarr/radarr, and therefore used short names and direct ports. After, they needed to use the full url, 443, ssl. Went into requestrr to update the url, then clicked test, success. Went to save, it gave an error that not all fields were populated. When I went to look at the categories, I see that the paths and profiles weren't populating. When I clicked "Load" it just flashed for a second then nothing. I think it was still trying to hit the old url, and I couldn't save the new url because of the form error.

To work around this I stopped requestrr and edited the settings direct in the settings.json file then restarted, and all was happy again. But might be a scenario you want to look into.

If this is the case, might be good to have a save next to the test button just for the core connection info for sonarr/radarr.

[thomst08]

That's an interesting find... I will have to look into that, I'll let you know if I find anything.

[inhumantsar]

i ran into this as well and can add some context. in my case, i moved everything to a new host and haven't set up SSL certs. the previous host had valid certs. when i try to update the host settings for radarr, partly to turn off "Use SSL", the connection test passes but all attempts to load profiles, categories, etc. get a 400 back.

this seems to be happening because the connection test posted to the requestrr backend with useSSL: false but the requests to load information from radarr have useSSL: true set.

# payload for POST requestrr/api/movies/radarr/test
{"Hostname":"sazed","BaseUrl":"/radarr","Port":80,"ApiKey":"snip","UseSSL":false,"Version":"3"}

HTTP 200

# payload for POST requestrr/api/movies/radarr/rootpath, .../profile, and .../tag
{"Hostname":"sazed","BaseUrl":"/radarr","Port":80,"ApiKey":"snip","UseSSL":true,"Version":"3"}

HTTP 400 "Could not load the paths from Radarr, check your settings."

maybe useSSL is hardcoded somewhere or there's some frontend state that's not getting updated?

also FWIW, this didn't happen with sonarr, only radarr. my sonarr and radarr instances were rebuilt from scratch, it's possible that sonarr's profile set was the same on the old instance while radarr's was different. might be related.