Sonarr3 Docker on Synology

Sonarr version (exact version): Can’t tell, dowloaded linuxserver/sonarr1 docker today.
Mono version (if Sonarr is not running on Windows): 5.18.0.240*12
OS: DSM 6.22-24922 (release 4)
Debug logs:
Description of issue: I cannot connect to the docker instance, possibly complicated by using a reverse proxy.

When I setup Sonarr3 on my Synology I setup a reverse proxy (my Synology is set to use https exclusively). I set the docker instance to listen on port 8888 and the reverse proxy to listen on 8899.

(I have other dockers running that do this as well, and they work, so I do not think he issue is the reverse proxy)

Sonarr3 is running in the docker and I can see that it is logging

[Info] RssSyncService: RSS Sync Completed. Reports found: 0, Reports grabbed: 0

from the command line on the Synology, it appears the web UI is not running:

# curl http://127.0.0.1:8888
curl: (56) Recv failure: Connection reset by peer
#

When I go to /volume/docker/sonarr3` and look at config.xml it appears to be the default config.

<Config>
  <LogLevel>Info</LogLevel>
  <Port>8989</Port>
  <UrlBase></UrlBase>
  <BindAddress>*</BindAddress>
  <SslPort>9898</SslPort>
  <EnableSsl>False</EnableSsl>
  <ApiKey>49144c45ceb0446aa652a3c1b003b303</ApiKey>
  <AuthenticationMethod>None</AuthenticationMethod>
  <Branch>master</Branch>
</Config>

This does not match what I see in the Synology dockerUI at all. There I have the paths setup as docker/sonarr3 => /config
Media/TV => /TV
download/Complete => /downloads

local port : 8888 => container port 8888

HOME : docker/sonar3
tz : america/Denver

and nothing else was changed.

The reverse proxy takes https://www.domain.tld:8889/ and maps it to http://myip:8888/

I haven’t spent a lot of time on the reverse proxy portion since the curl command from the command line doesn’t return anything that looks like a web server.

If the config file is saying it’s running on port 8989 then trying to access it at port 8888 isn’t going to work, you’re going to have to change the port in the config and restart Sonarr or the reverse proxy.

yeah, for some reason it was not writing the config file. I did get it working by specifying a different path for /config, but then it turned out the docker image is for Sonarr 2.0.0.5338. Replacing it with a 3.0.3-664-is157 and see if that work.

Looks like updating will require replacing the docker each time?

Yeah, to upgrade from v2 to v3 you do and from v3 to another version of v3 you will as well (with docker at least). Docker Compose is helpful with that, not sure if it’s available on synology without going through some hoops.

I can at least connect to Sonarr, but when I try to scan for existing series nothing happens….

[DELETE]

I resolved this by using the UID/GID that sonarr2 was using on the Synology. (122507:100)

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.