Sonarr/mono update broke sonarr

Currently reading
Sonarr/mono update broke sonarr

25
5
NAS
DS1019+, DS916+
Operating system
  1. Windows
Mobile operating system
  1. Android
  2. iOS
I run Sonarr as a package. (yes, I know - run it in Docker. I don't want to dismantle the Sonarr that's been running fine for years, unless I have absolutely no other choice. I've found that trying to restore a Sonarr backup hasn't worked for me, the 2 times I've tried it. And I don't want to have to re-enter many TV shows, until I have to ....)

Anyway, I solved the first problem - updating mono's certificates. Now Sonarr is accessing my indexers again. But what's happening is that an episode will be downloaded (I use SABnzd, also as a package). And the download finishes, but Sonarr never renames the file and moves it to the media folder. I believe it's a permissions problem:

2022-10-11 05:10:31.7|Error|VideoFileInfoReader|Unable to parse media info from file: /volume1/downloads/complete/the.patient.s01e08.1080p.web.h264-cakes/32e11a0658d44d23a9ca61b3d6155d9b.mkv
[v3.0.6.1265] System.UnauthorizedAccessException: Access to the path "/volume1/downloads/complete/the.patient.s01e08.1080p.web.h264-cakes/32e11a0658d44d23a9ca61b3d6155d9b.mkv" is denied.

So in checking the "downloads" shared folder, I don't see either "sc-download" or "sc-nzbdrone" in the permissions. So I manually added both to each folder in the "downloads" path, and gave it all permissions. I think this will resolve the problem. (I hope - I have to wait for new episodes to be released, before I can fully close this out). I also tried setting the Media Management perms in Sonarr settings to 777, but that didn't help.

Am I the only one having this problem? Is my solution the way to fix it?

I may look into setting up Docker and running sonarr that way, but until I can do that, and make sure it imports all my many shows, I need to get this to run in the meantime.
 
Am I the only one having this problem? Is my solution the way to fix it?
This is a clear permissions issue and yes, adding some should solve it.

I've found that trying to restore a Sonarr backup hasn't worked for me
Migration from bare-metal install/config to a docker one is fully supported and should work just fine if you follow the official guide on the matter. Done it more then a few times (same with any other xxxxRR app) and it works without issues.
 
Follow this guide and set up a local docker user on your Synology NAS, and set the permissions on your files / shares so the "docker user" is owner. Then set your Sonarr environment variables to the PUID and PGID of the docker user account.

 
This is a clear permissions issue and yes, adding some should solve it.

Yeah, I tried adding both the "sc-download" and "sc-nzbdrone" to the "downloads" folder and to the media folder, but that didn't help. If I do it manually - i.e., an interactive search, and choose a download - that all works fine; file downloads, gets renamed, moved to the media folder. When Sonarr does it programmatically, it doesn't - the file gets downloaded, but never renamed or moved.

Migration from bare-metal install/config to a docker one is fully supported and should work just fine if you follow the official guide on the matter. Done it more then a few times (same with any other xxxxRR app) and it works without issues.

I tried setting up a Docker container for Sonarr following this site:

The only difference is that I set it to be port 9898, rather than 8989, since I can still use the Sonarr package interactively, so I didn't want to change the existing setup until I had a working replacement. And it says that Sonarr is running, but I can't connect on "https://<NAS-IP>:9898". It refuses. Dunno if that was because I set it to use a new bridge network, rather than the host network, as that guide recommends. It was late, and I got fed up. :)

When I get home from work today, I'll have to look into it. What would be the "official" guide? Is it this:


This doesn't seem to say anything about Sonarr; did I miss something?

I share my Plex with a number of family members, so there are a lot of different shows I have Sonarr follow. I really don't want to have to manually enter them all into a new Sonarr configuration, if I don't have to.

Thanks!
 
it says that Sonarr is running, but I can't connect on "https://<NAS-IP>:9898". It refuses
You did everything right. The idea is to have multiple Sonarr instance running while migrating, and once you have it all good and sorted then you can stop the bare metal one.

The fact that it refsuses to connect is not because of the bridge network, but it might be a firewall issue either on the desktop side (not likely), or on the DSM itself. If the DSM FW is active, make sure that the local subnet doesn't have docker "bridge" network (or any other for that matter) blocked.

It is a common issue with hardend FW settings that will block and refuse connections from resources running in Docker.

Also, what exact error do you get?

Finally, once you do the migration (and sort the connection), you will see that the setup, config and the rest will all transfer over without issues.
 
The fact that it refuses to connect is not because of the bridge network, but it might be a firewall issue either on the desktop side (not likely), or on the DSM itself. If the DSM FW is active, make sure that the local subnet doesn't have docker "bridge" network (or any other for that matter) blocked.

It is a common issue with hardened FW settings that will block and refuse connections from resources running in Docker.

OK. I do have the Synology firewall enabled (I'm not totally crazy ... LOL). And I did create a new rule:

All ports, all protocol, source IP 172.20.0.1 to 172.20.255.254, Allow

That's because I set the bridge network to be 172.20.0.0/16 with a gateway of 172.20.0.1. And I set the container to use this bridge network.

The Synology itself is 10.0.0.xx.

Also, what exact error do you get?

I'll have to wait until I get home to check, I don't have the VPN on the Synology set up yet to access it remotely. I was entering "https://10.0.0.xx:9898".

Finally, once you do the migration (and sort the connection), you will see that the setup, config and the rest will all transfer over without issues.

That would be ideal! I have SABnzd and Radarr running as packages, and they work, and I don't want to touch them ever again. LOL (for updates, I mean). If I have to, I'll make containers out of them when the time comes.

Thanks for all the help!
 
Last edited:
More info: if I look at the sonarr.txt file in the "logs" folder under "sonarr" in "docker", I see this:

2022-10-13 09:30:55.0|Info|OwinHostController|Listening on the following URLs:
2022-10-13 09:30:55.0|Info|OwinHostController| http://*:8989/
2022-10-13 09:30:56.2|Info|SonarrBootstrapper|Starting Web Server

The config.xml shows the SSL port as 9898, but it also says SSL isn't enabled .... Maybe that's why it refused to connect.

<Config>
<LogLevel>info</LogLevel>
<EnableSsl>False</EnableSsl>
<Port>8989</Port>
<SslPort>9898</SslPort>
<UrlBase></UrlBase>
<BindAddress>*</BindAddress>
<ApiKey>ec7fee08458e49fba7d20f83565678c8</ApiKey>
<AuthenticationMethod>None</AuthenticationMethod>
<UpdateMechanism>Docker</UpdateMechanism>
<LaunchBrowser>True</LaunchBrowser>
<Branch>main</Branch>
<SslCertHash></SslCertHash>
<InstanceName>Sonarr</InstanceName>
<SyslogPort>514</SyslogPort>
</Config>

I'll stop the container, enable SSL, restart the container, and check tonight ...
(I really must finish configuring the VPN, so I can test this stuff remotely. I just need to forward the ports on my router ....)
-- post merged: --

I think that may have done it, although I won't be able to connect until later tonight. But the sonarr log now says:

2022-10-13 11:18:16.2|Info|OwinHostController|Listening on the following URLs:
2022-10-13 11:18:16.2|Info|OwinHostController| http://*:8989/
2022-10-13 11:18:16.2|Info|OwinHostController| https://*:9898/
2022-10-13 11:18:17.2|Info|SonarrBootstrapper|Starting Web Server

So maybe now it will connect. :cool:
 
Last edited:
Have you tried Docker? Much simpler and no dependency (or Synology) issues.
Yes, if you go through the thread, I am trying to get Docker to work, as a replacement. But it's not working yet, either.
 
I am trying to get Docker to work, as a replacement.
Still not able to access "https://10.0.0.xx:9898":
It's unclear to me what you are trying here in docker. Did you set up your port as 9898:8989 (not 9898:9898)?

If so, have you tried to connect as http://<nas_lan_ip>:9898

What is the point of https? Are you accessing remotely? If you are, you should get local access resolved first.
 
Last edited:
It's unclear to me what you are trying here in docker. Did you set up your port as 9898:8989 (not 9898:9898)?

I set the port to be 9898:9898, as the Sonarr community package that is still running is using the 8989, and I don't want to interfere with the package, until the Docker works. But right now, the Docker Sonarr doesn't even respond.

If so, have you tried to connect as http://<nas_lan_ip>:9898


What is the point of https? Are you accessing remotely? If you are, you should get local access resolved first.

I access all sites using https, my browser even defaults to it. No, I am not accessing remotely, this is all internal.
I will try the http:// instead of https://, I'll just have to remember to turn off SSL enforcement for this site (which I don't have to do with the community package version).
 
You cannot change the second value. It is specific to the container!

This is what I see, in the details of my container:

1665766303034.png


In the Sonarr config.xml, I see the regular port of 8989 and the SSL port is listed as 9898. That's why I was trying to use https://<NAS>:9898.
 
Last edited:
NEVER change the internal container port. This is likely the primary cause of your docker issues. Only change the external port (if nece

I meant change the internal port back to 8989

so it looks like

1665775577390.png

-- post merged: --

So one more question. Right now, my Sonarr moves media to a shared folder on my volume1 (called TV-Shows-2020-DS1019). How do I map that to my container? If I restore my Sonarr config from the package to the container, won't it try and put new episodes in "volume1\TV-Shows..."? But that's not how it's mapped to the container - in mapping, I only see the shared folder name (TV-Shows...), and not that path.

Am I worrying unnecessarily? Will this just be a seamless restore of settings, and list of shows?
 
ThkuaYc.png


You don't type this in (left side), but use the drop-down to navigate to the folder which has your shows.

Mine is simple "TV Shows". No need to complicate that any further. I recommend following the Plex naming convention for best overall experience (metadata, etc.).

Yeah, I have a couple Plex servers, one just for me, one for the people I share out with; both access the same data, it's just the server load that is different. Also I have my media spread across 2 NASes, my old DS916 with old media+ and my current DS1019+ with current and future media. Hence the odd naming, so I can see at a glance which NAS and folder I'm on. :) These folders have been in place and working well with Plex for years now.

OK, are there any other volume mappings I should set? This is the first tutorial I've seen that mentions either "/tv" or "/downloads" as mount paths.
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Similar threads

Much simpler to run these as docker containers. Otherwise, I cannot help.
Replies
1
Views
2,570
I'm running the SynoCommunity packaged Sonarr v3.0.6.1355 with the SynoCommunity packaged Mono v5.20.1.34...
Replies
0
Views
2,628
Guessing Mono got updated as well as sonarr, but they don't play well any more depending on the mono...
Replies
2
Views
2,615

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Back
Top