PhAzE

Have you rebooted the server also? That will need to be done to remove the old mono files. Are you on Unraid 5?

When you did a fresh install, did you set a different config directory so you are using a fresh db as well?

It's the latest version that they host on their site. I'll take a look to see of the URL changed later today.

Cool thanks!

If you roll it back just beware you will likely need to delete your db and start fresh. I don't think you should make it default to an older version but tagging is a great idea! How do I do that exactly though?

There have been reports of these failing on 6.2 beta and I haven't had time to test on that version yet unfortunately. Can you post the exact logs just before the install file missing error?

dSUB works perfectly with Madsonic, however Madsonic is now updated to version 6.0 recently. The update from 5.x to 6.x broke my DB, and now enabled a premium license trial. Once that trial is over, dSUB will stop working because Madsonic disables API support. Rather ridiculous. Oh, and you can't buy a premium license since the dev hasn't opened it up for another 3 months time. The trial expires in 30 days though. /Rant It seems that Madsonic 6.0 transcoder isn't working in this docker at the moment. Not a big deal unless you use FLAC, it seems to have the windows .exe of ffmpeg instead.

My instance seems to stop working quite often, how is the service / app watched? Is it using supervisord or some other method to keep the service alive?

Yes, of you have been upgrading one of them it might have files that are no longer included by sonarr where a new fresh install wouldn't have those files.

Mozroot.exe is mono's import took for certificates, if that's any help. Try on Unraid 6 to confirm. Perhaps user another USB with 6.1.9 installed on trial.

First, stop all my plugins and then delete the /usr/local/PhAzE-Common directory. Then empty the install directory. Leave your config directory alone. Start them up and see if sonarr works. If not, stop it again, move your config folder a somewhere else for now and see if it starts fresh (possible db corruption). If it starts, your db was corrupted. And lastly, set your config and install directories to /mnt/disk1/... instead of/mnt/user and see if that helps. Do that if the other fixes don't work.

Is this a fresh install of sonarr? Can you post your config directory and install directory locations and if you have a cache drive available?

Could be a problem with mono and your hardware. From command line try: Sonarr-env mono -V And see what comes up. That will run mono version check under the sonarr environment.

Just restart the app actually

Are you still seeing this problem since the last plugin update? When I test it, it seems to remember with the eception of a fresh install, starting up for the first time, plex automatically turns that option off. Once you set it back on you can restart without it forgetting. Nevermind, I found the problem. It was a missing equals sign on the use port variable. Should be good after the next update.

Are you still seeing this problem since the last plugin update? When I test it, it seems to remember with the eception of a fresh install, starting up for the first time, plex automatically turns that option off. Once you set it back on you can restart without it forgetting.

You should see a big blue "update plugin" button appear in the emby settings page shortly. Click that, and all will be well in the world.

I'll fix it, give me a minute.

It's included already Ninja edit: unless you are on the new beta... I haven't had time to test on that version yet.

Also, that folders won't exist until you start the app once, which then they will be created.

Leave images, cache, metadata, and transcode blank. They will default to a folder under the config folder. You only need to specify them if you want them in a different folder than the defaults. As long as your config folder is in your cache drive, you're good. As for install folder, is on to leave that under usr/local/ because the actual install files are stored in the USB, so they don't get downloaded each time, only once. If you want to move install folder to your cache drive, that will work also but you don't need to.

Ah that explains the problem i was having with Ubooquity also. Removed container and image, deleted template, added from CA again, and all good now.

Make sure the config/library directory is set to a path on a physical drive, very like your cache drive. It should not remain on the ram drive under /usr/local. That ram drive is erased and recreated in each reboot of Unraid. Docker and plugin do basically the same thing but different approaches to doing it. Also made by different people.

Thanks, I'll check it out tomorrow

Yes it does