Unable to launch with config.yaml

[mikevipe]

Hello I am unable to launch no matter what I do with the edited default config.yaml:

I get the following error:
06:43:30.720 [io-compute-22] ERROR configuration.ConfigurationUtils$ - Unable to connect to Sonarr at host.docker.internal:8989, with error java.net.ConnectException: Connection refused
java.lang.IllegalArgumentException: Unable to connect to Sonarr at host.docker.internal:8989, with error java.net.ConnectException: Connection refused

I can see in debug that the config is mounted:
2024-06-26T23:39:19.427238227-07:00 volume unmount config (container=70a9f08548668274fb142d60110261d05a522b07551daf37dfdff5a1524098da, driver=local)

I have my config in:
/var/lib/docker/volumes/config/_data/config.yaml (where the system auto creates)

docker inspect shows that is the correct directory:
"Mounts": [
{
"Type": "volume",
"Name": "config",
"Source": "/var/lib/docker/docker/volumes/config/_data",
"Destination": "/app/config",
"Driver": "local",
"Mode": "z",
"RW": true,
"Propagation": ""
}
],

I am at a loss, I have no idea at this point why it will not work.

I am starting with the command:
docker run -v config:/app/config nylonee/watchlistarr

Even starting with the direct options does not work:

docker run -e SONARR_BASE_URL=http://192.168.15.2:30027 -v config:/app/config nylonee/watchlistarr

07:08:01.190 [io-compute-10] ERROR configuration.ConfigurationUtils$ - Unable to connect to Sonarr at host.docker.internal:8989, with error java.net.ConnectException: Connection refused
java.lang.IllegalArgumentException: Unable to connect to Sonarr at host.docker.internal:8989, with error java.net.ConnectException: Connection refused

Any help is appreciated.

Thanks

[nylonee]

Hello! There's a very good chance that your config mounting is correct, but it's unable to find your Sonarr URL (and eventually your Radarr URL, assuming they're hosted the same way).

It might be worth reviewing where your Sonarr instance is hosted, and ensuring that docker can reach Sonarr.

[nylonee]

The config logs are certainly confusing. What it does is it tries your URL you provided, but if it doesn't work it'll try a bunch of other "usual" values, eventually ending and erroring with one that doesn't look like the config you put in.