CHBMB

Path for sonarr in Bazarr settings should be /media

Load your site in the browser and check the cert in Chrome/Firefox Sent from my Mi A1 using Tapatalk

Post your sonarr docker container settings.

Yeah the link is wrong, I'll fix it, should be https://hub.docker.com/r/linuxserver/piwigo/

Might be worth checking your wireguard config. I've got WireGuard set up on both Unraid and my firewall (Opnsense) and can access Unifi just fine, however a couple of times when I've misconfigured it I've managed to take out my whole network. Sent from my Mi A1 using Tapatalk

docker exec -it plex bash apt update apt install sqlite Then do whatever you need to do.

I don't use Plex and am on mobile atm so difficult to do much. It would probably be easier to roll back to a backup. If you don't have backups then I would definitely make some before you attempt any database repair. Sent from my Mi A1 using Tapatalk

https://support.plex.tv/articles/202796273-why-are-there-old-or-duplicate-server-entries-in-the-dashboard-sidebar/ It's because you've installed a different PMS container, Plex thinks you have two different servers.

Not that I'm aware of. And you haven't really done much in the way of setup, probably as easy to nuke and pave.

As an aside I know our container has some advantages that the LT version doesn't if you end up using hardware transcoding

This is the support thread for the LinuxServer version of Plex, the run command you posted is for the LimeTech version of Plex. Depending on how you look at it, you're either in the wrong thread (Use the LimeTech support thread) or you've configured your machine incorrectly (You should be using our version)

More to the point, you're not even using the LinuxServer container 'limetech/plex'

Post your docker run command, link to this is in my signature, you may need to enable signatures on your forum setting. Sent from my Mi A1 using Tapatalk

See the post above yours tvdb changed their API Sent from my Mi A1 using Tapatalk

You'd have to make your own proxy config file if we don't have one (I haven't checked) but in theory it should be possible. Although you don't need to for the VPN to work, just the VPN port forwards, the webui port can remain closed and only LAN accessible.

OK, so identical to me, so things that might be worth looking at that could potentially be different. config.php nextcloud reverse proxy conf Nextcloud version (I'm on 17) Default file If you post I'll check, but I need a bit more to go on.

How are you reverse proxying it?

For the warnings then delete the `default` file and it will be recreated on container restart. Alternatively take a look at the version on Github.

I don't think we need them, if it were a widespread issue, we'd have heard by now. As it stands a solitary report I don't think justifies a conclusion of the container logic not handling things well. If the API/certbot had an issue, no amount of rewriting of the container is going to fix that.

I understand you don't want to compile yourself, but I don't particularly want to compile any more than the exisiting four/five builds I do with every release. If these kernel modifications are needed then they should be pushed upstream to LimeTech.

Reading the article it sounds like a previously known vulnerability is used to implement the malware. We've already patched it and posted on our blog about it. https://blog.linuxserver.io/2019/10/26/psa-nextcloud/ I suggest you all read that and implement, this does highlight one point I've been making for a long time, once you spin up these services, whether you understand how to or not, you become the sysadmin and need to be able to keep things up to date. TL:DR I think it's using a known vulnerability to encrypt things, but that hasn't been confirmed yet, so you need to decide on how you want to approach this issue and when you feel the risk is acceptable to keep/bring back your Nextcloud server online. Sent from my Mi A1 using Tapatalk

No idea. Sent from my Mi A1 using Tapatalk

Can;t tell you exactly what the problem is but this is probably relevant. https://serverfault.com/a/396847 I'd recheck your config, I suspect you've missed a setting that is incorrect.

Check your /config/nginx/logs/ folder to see what that says. That IO error is a bit concerning, makes me wonder if your appdata has become a bit corrupted.

Logs for why the connection is failing would be my first suggestion. Otherwise not much to go on.