CHBMB

Yeah, even if the underlying Booksonic code isn't updated. the container still receives updates. If/when he releases another project to replace Booksonic in it's current guise then we'll obviously reassess things, but from your point of view at the moment, nothing has changed. It's not really as though booksonic has seen much dev over the last few years anyway.

That was fixed a while ago https://github.com/linuxserver/docker-booksonic/pull/16

I haven't done this for a few years, but iirc I hosed everything except my user data and then used occ to scan everything back in after afterwards. Sent from my Mi A1 using Tapatalk

If it were me, I'd first make sure stuff is backed up then try running the full upgrade from the CLI

@levster What version were you on? Because if you were on 15 and trying to upgrade to 17 that would explain the error.

If you're sure you're running the latest version of our container then it must be a sickchill issue as we're building from master and it's up to date. https://github.com/SickChill/SickChill/commits/master https://github.com/linuxserver/docker-sickchill/releases/tag/2c72459d-ls28

Nextcloud is an exception for technical reasons. Sent from my Mi A1 using Tapatalk

If you read the first post, this is discussed with links. Sent from my Mi A1 using Tapatalk

There probably is, but I don't know how. I still think it's a client side issue tbh.

That's an error with LetsEncrypt, nothing to do with Nextcloud. You're not going to be able to get any further until you sort that out. Suggest you post in the LetsEncrypt support thread, including the above log and with your docker run command (see the docker faq to find out how to get that) and screenshots of your port forwards in your router/firewall.

So it's working? Sent from my Mi A1 using Tapatalk

That thread is in reference to the desktop client. libgnome-keyring is a Linux desktop package for the Gnome desktop. So basically nothing related to your problem with Windows clients

Try the terminal, it's more reliable in general.

Docker run command for both is required. You can see how by either turning on signatures in the forum, and the link is in mine, or by reading the docker faq. Sent from my Mi A1 using Tapatalk

You could always submit a pull request to change it.

You're not changing the port in the webui are you? Otherwise as @trurl says, post your docker run command.

@Nimrad Don't restart via the webui, restart the docker container via the Unraid interface.

So you 100% sure that RC9 works and v6.8.0 doesn't, that's weird as I used the same config. Sent from my Mi A1 using Tapatalk

Post over in the DVB thread then, it's not a Plex issue. it's a DVB issue. Can you try one of the RC builds as well, perhaps RC8?

You're going to have to try it and see and do some reading about DVB in Plex. They only support a limited number of tuners, and Linux itself doesn't support every tv tuner, so you need to make sure there are Linux drivers

Depends on your TV tuner. Probably LibreELEC if it's a supported tuner in there and in Plex.

Just as well, cos I can't show you my setup as I don't use it.....

For Bazarr container settings make /media = /mnt/user/Media Need to be referencing the same place. Then configure Bazarr in the webui with wherever Radarr thinks your movies are /media/Movies whatever? You need to read the Docker FAQ and make sure you understand docker volume mappings, currently you don't, which is why you're struggling and you'll have problems with all containers if you don't grasp the concept

That is your issue. /dev/dvb/ is your tv tuner.

You download it and reboot. That's all there is to it.