CHBMB

Look at the link on the first post to upgrade, that uses occ. Sent from my LG-H815 using Tapatalk

Check the link in the first post.

No Sent from my LG-H815 using Tapatalk

Upgrade the container as well, that updates the other components of the Nextcloud container other than Nextcloud, like Nginx and dependencies. Sent from my LG-H815 using Tapatalk

Use the command line mode linked in the first post. Sent from my LG-H815 using Tapatalk

That's hardware and TVH dependent, docker doesn't limit you.

Well, you're the only one who's reported an error, so it's better work than your backup strategy if it's upset you that much. Sent from my LG-H815 using Tapatalk

Why you posting in multiple places? Answered in your other post.

This is kind of beyond the scope of what I'd consider support, but I guess if I were you, this is what I'd do. Make sure the permissions are 0770on the host, as well as checking who owns the files/folders. On unraid they'll need to be owned by nobody:users so you could change them on the host to that.

How are you mounting the Nextcloud folder?

No, I know which file is which, I wrote an older guide which may be helpful, it's based on Apache but the config.php is there for the setup you're looking at. <?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'xxxxxxxxxxxx', 'passwordsalt' => 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx', 'secret' => 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx', 'trusted_domains' => array ( 0 => '192.168.0.1:444', 1 => 'server.com', ), 'overwrite.cli.url' => 'https://server.com', 'overwritehost' => 'server.com', 'overwriteprotocol' => 'https', 'overwritewebroot' => '/nextcloud', 'dbtype' => 'mysql', 'version' => '9.0.52.0', 'dbname' => 'nextcloud', 'dbhost' => '192.168.0.1:3305', 'dbtableprefix' => 'oc_', 'dbuser' => 'oc_CHBMB1', 'dbpassword' => 'xxxxxxxxxxxxxxxxxxxx', 'logtimezone' => 'UTC', 'installed' => true, );

That config.php is very complex with multiple domains. Why don't you simplify it, and use the guide as an example and get that working first, before adding in proxies and stuff. To be honest, you're either very experienced with webserver setup and proxies and know what you're doing or things have just got way more complicated than they need to with that setup. But really, I don't see how we can help with such a complex setup. Here's the config.php I used, for one domain, not using /nextcloud <?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'xxxxxxxxxxxx', 'passwordsalt' => 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx', 'secret' => 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx', 'trusted_domains' => array ( 0 => '192.168.0.1:444', 1 => 'nextcloud.server.com', ), 'overwrite.cli.url' => 'https://nextcloud.server.com', 'overwritehost' => 'nextcloud.server.com', 'overwriteprotocol' => 'https', 'dbtype' => 'mysql', 'version' => '11.0.1.2', 'dbname' => 'nextcloud', 'dbhost' => '192.168.0.1:3305', 'dbport' => '', 'dbtableprefix' => 'oc_', 'dbuser' => 'oc_CHBMB1', 'dbpassword' => 'xxxxxxxxxxxxxxxxxxxx', 'logtimezone' => 'UTC', 'installed' => true, ); You'd still need to add 'overwritewebroot' => '/nextcloud',

Without seeing config files it's impossible to say. But I know that you must have a mistake in them somewhere. To be honest, there are only two config files changed in my guide, so that should narrow it down. FWIW the reasons you've outlined don't make sense to me, using LetsEncrypt you can get certs for extra subdomains as long as you define them in your domain providers config and if you're running Nextcloud behind a reverse proxy you only need to forward 443 anyway. For instance I run about 5 different subomains, as you can see only 1 SSL cert in LetsEncrypt and only port 443. Nginx in the LetsEncrypt container handles the virtual servers. WAN ==> 443 ==> LetsEncrypt==> nextcloud.server.com ==> photos.server.com ==> files.server.com ==> server.com ==> books.server.com

Some error following the guide I'm going to guess. And also, that's not following the guide in the first post, as I don't support putting nextcloud in a subfolder, which is what you're describing.

Hmmm, never answered my question.....

Then you're kind of on your own, please tell me you're at least using our Tautulli container?

I dunno, you tried playing some stuff in Plex and seeing if it updates. Also I don't know about other versions of Plex and Tautulli other than the Linuxserver.io ones, I suppose there could be permission issues with other containers.

You looked at this guide? I only use OTA EPG so can't help. https://www.linuxserver.io/2017/02/19/how-to-set-up-tvheadend-with-your-dvb-t2-receiver/ If you're still having problems after following this, maybe @Stark can help.

Also.... Firstly /mnt/user/appdata/plexpy/logs/":"/logs You should be mapping /logs to the Plex container logs, not plexpy logs. Try: /mnt/user/appdata/plex/Library/Application Support/Plex Media Server/Logs/ Secondly change your appdata from /mnt/user/ to either /mnt/cache/ or /mnt/disk1/ or /mnt/disk2/ depending on what DISK your appdata is actually on, SQLite doesn't play well with /mnt/user/

It tells you why in the log.

picons are included.

I don't support that tutorial. Either follow the tutorial I wrote, linked on the first post of thus thread or get support from Cyanlabs themselves if you follow that tutorial. Sent from my LG-H815 using Tapatalk

You can remove the container and image, it's only the appdata that shouldn't be removed. You could remove it, then stop Tautulli, rename the plexpy appdata folder to tautulli and then edit your tautulli template and point it to the renamed folder..... Sent from my LG-H815 using Tapatalk

Unassigned Devices.... The clue is in the name, they're unassigned to the array. Not sure how well NTFS will work though. Sent from my LG-H815 using Tapatalk

You don't need to I don't think, mount the drive with Unassigned Devices. Sent from my LG-H815 using Tapatalk