EdgarWallace

Great @Irmn I am going to check this out as soon as I am having a little bit of time. Question: I was hoping to get rid of NGINX?

My Nextcloud environment on unRAID has been running well for years, I run the lsio variant and have Collabora running as an extra Docker. In the meantime, I have switched all dockers that I want to reach from outside my network to tailscale. To be able to switch off port forwarding and NPM, it would now be the turn of these two dockers. I have the same settings as the topic creator and get the same error messages. I have also adapted my config.php: <?php $CONFIG = array ( 'datadirectory' => '/data', 'instanceid' => 'xxxxxxxxxxxxxxxxxxxxxx', 'passwordsalt' => 'xxxxxxxxxxxxxxxxxxxxxx', 'secret' => 'xxxxxxxxxxxxxxxxxxxxxx', 'trusted_proxies' => array ( 0 => 'xxx.xxx.xxx.xxx', ), 'trusted_domains' => array ( 0 => 'xxx.xxx.xxx.xxx:444', 1 => 'mynetwork.com', 2 => '100.xxx.xxx.xxx:444', 3 => 'nextcloud.tailscalenetwork.ts.net', ), 'overwrite.cli.url' => 'https://mynetwork.com', 'overwritehost' => 'mynetwork.com', 'overwriteprotocol' => 'https', 'dbtype' => 'mysql', 'version' => '31.0.2.1', 'dbname' => 'nextcloud', 'dbhost' => 'xxx.xxx.xxx.xxx:3306', 'dbport' => '', 'dbtableprefix' => 'oc_', 'dbuser' => 'xxxxxxxxxxxxxxxxxxxxxx', 'dbpassword' => 'xxxxxxxxxxxxxxxxxxxxxx', 'allow_local_remote_servers' => true, 'auth.bruteforce.protection.enabled' => true, 'ratelimit.protection.enabled' => true, 'default_language' => 'de_DE', 'default_locale' => 'de', 'default_phone_region' => 'CH', 'mysql.utf8mb4' => true, 'installed' => true, 'maintenance' => false, 'defaultapp' => 'files', 'knowledgebaseenabled' => true, 'enable_avatars' => true, 'allow_user_to_change_display_name' => true, 'loglevel' => 3, 'logfile' => '/config/nextcloud.log', 'logfilemode' => 416, 'logtimezone' => 'Europe/Berlin', 'appstoreenabled' => true, 'updater.release.channel' => 'stable', 'updater.server.url' => 'https://updates.nextcloud.com/updater_server/', 'theme' => '', 'mail_smtpmode' => 'smtp', 'mail_smtpsecure' => 'tls', 'mail_smtpauthtype' => 'LOGIN', 'ldapIgnoreNamingRules' => false, 'encryption.legacy_format_support' => false, 'encryption.key_storage_migrated' => false, 'mail_from_address' => 'xxxxxxxxxxxxxxxxxxxxxx', 'mail_sendmailmode' => 'smtp', 'mail_domain' => 'xxxxxxxxxxxxxxxxxxxxxx', 'mail_smtphost' => 'xxxxxxxxxxxxxxxxxxxxxx', 'mail_smtpport' => '587', 'mail_smtpauth' => 1, 'mail_smtpname' => 'xxxxxxxxxxxxxxxxxxxxxx', 'mail_smtppassword' => 'xxxxxxxxxxxxxxxxxxxxxx', 'memcache.local' => '\\OC\\Memcache\\APCu', 'memcache.distributed' => '\\OC\\Memcache\\Redis', 'memcache.locking' => '\\OC\\Memcache\\Redis', 'redis' => array ( 'host' => 'xxx.xxx.xxx.xxx', 'port' => 6379, ), 'filelocking.enabled' => 'true', 'updater.secret' => 'xxxxxxxxxxxxxxxxxxxxxx', 'memories.exiftool' => '/config/www/nextcloud/apps/memories/exiftool-bin/exiftool-amd64-musl', 'memories.vod.path' => '/config/www/nextcloud/apps/memories/exiftool-bin/go-vod-amd64', 'memories.vod.ffmpeg' => '/usr/bin/ffmpeg', 'memories.vod.ffprobe' => '/usr/bin/ffprobe', 'enable_previews' => true, 'enabledPreviewProviders' => array ( 1 => 'OC\\Preview\\HEIC', 2 => 'OC\\Preview\\PDF', 3 => 'OC\\Preview\\XBitmap', 4 => 'OC\\Preview\\PNG', 5 => 'OC\\Preview\\Image', 6 => 'OC\\Preview\\Photoshop', 7 => 'OC\\Preview\\TIFF', 8 => 'OC\\Preview\\SVG', 9 => 'OC\\Preview\\BMP', 10 => 'OC\\Preview\\GIF', 11 => 'OC\\Preview\\JPEG', ), 'memories.index.path' => '/fotos/', 'upgrade.disable-web' => true, 'maintenance_window_start' => 1, 'app_install_overwrite' => array ( 0 => 'imageconverter', 1 => 'talk_simple_poll', 2 => 'unsplash', 3 => 'groupfolders', 4 => 'integration_collaboard', 5 => 'tasks', ), ); Maybe it's important to modify overwrite.cli.url and overwritehost as well?

Share Cloud_Data set to not use the cache, but files / folders exist on the cache drive There are a few more shares and I followed these steps which are recommended: Stop Docker and VM services in Settings Change the settings of the share to Use Cache: yes and then run mover. After mover has finished, set the use cache settings back to no and enable the docker and VM services again. Btw a scrub of the cache drives ended with 0 errors Help is much appreciated.

Making the setting of Sortable Items on the dashboard persistent. Seems that the settings are saved via browser cookie.

Yes - everytime I am closing my browser. Alright I think that I am going to mark this as closed - works as designed.

Thanks @JorgeB my issue is that this approach doesn‘t survive a reboot. Eeven closing and reopening the browser is setting everything back to standard (= showing everything). I was expecting that my settings would be persistent.

Is there a way (or is it planned) to permanently set the sortable items in the dashboard? I would like to permanently hide some of the categories.

I hope that this is the correct forum. My guess is that I am using wrong NPM setting this is why... Just migrated from SWAG to NPM, all guides on page #1 have been read and the tests went well. DDNS and DNS settings (CNAME) are managed by all-inkl.com. I can reach calibre and emby dockers by using e.g. emby.mynetwork.com. Nextcloud is accessible under mynetwork.com. I have defined collabora.mynetwork.com but I can't open any files. This is not a surprise because Nextcloud isn't accepting the address collabora.mynetwork.com (Es konnte keine Verbindung zum Collabora Online-Server hergestellt werden). Some details: Nextcloud is the lsio docker which is based on alpine, hence can't use the integrated COLLABORA CODE. NPM - I was using the advanced setting from here: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/70 Collabora docker is showin OK by using entering collabora.mynetwork.com All dockers are BRIDGE Has anyone a well running setup using the same dockers? Nextcloud error: [richdocuments] Fehler: GuzzleHttp\Exception\ConnectException: cURL error 28: Connection timed out after 45001 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://collabora.mynetwork.com:9980/hosting/capabilities at <<closure>> 0. /app/www/public/3rdparty/guzzlehttp/guzzle/src/Handler/CurlFactory.php line 158 GuzzleHttp\Handler\CurlFactory::createRejection("*** sensitive parameters replaced ***") 1. /app/www/public/3rdparty/guzzlehttp/guzzle/src/Handler/CurlFactory.php line 110 GuzzleHttp\Handler\CurlFactory::finishError() 2. /app/www/public/3rdparty/guzzlehttp/guzzle/src/Handler/CurlHandler.php line 47 GuzzleHttp\Handler\CurlFactory::finish() 3. /app/www/public/3rdparty/guzzlehttp/guzzle/src/Middleware.php line 137 GuzzleHttp\Handler\CurlHandler->__invoke() 4. /app/www/public/lib/private/Http/Client/DnsPinMiddleware.php line 114 GuzzleHttp\Middleware::GuzzleHttp\{closure}("*** sensitive parameters replaced ***") 5. /app/www/public/3rdparty/guzzlehttp/guzzle/src/PrepareBodyMiddleware.php line 35 OC\Http\Client\DnsPinMiddleware->OC\Http\Client\{closure}("*** sensitive parameters replaced ***") 6. /app/www/public/3rdparty/guzzlehttp/guzzle/src/Middleware.php line 31 GuzzleHttp\PrepareBodyMiddleware->__invoke() 7. /app/www/public/3rdparty/guzzlehttp/guzzle/src/RedirectMiddleware.php line 71 GuzzleHttp\Middleware::GuzzleHttp\{closure}("*** sensitive parameters replaced ***") 8. /app/www/public/3rdparty/guzzlehttp/guzzle/src/Middleware.php line 63 GuzzleHttp\RedirectMiddleware->__invoke() 9. /app/www/public/3rdparty/guzzlehttp/guzzle/src/HandlerStack.php line 75 GuzzleHttp\Middleware::GuzzleHttp\{closure}("*** sensitive parameters replaced ***") 10. /app/www/public/3rdparty/guzzlehttp/guzzle/src/Client.php line 331 GuzzleHttp\HandlerStack->__invoke() 11. /app/www/public/3rdparty/guzzlehttp/guzzle/src/Client.php line 168 GuzzleHttp\Client->transfer() 12. /app/www/public/3rdparty/guzzlehttp/guzzle/src/Client.php line 187 GuzzleHttp\Client->requestAsync("*** sensitive parameters replaced ***") 13. /app/www/public/lib/private/Http/Client/Client.php line 226 GuzzleHttp\Client->request() 14. /config/www/nextcloud/apps/richdocuments/lib/Service/CapabilitiesService.php line 135 OC\Http\Client\Client->get() 15. /config/www/nextcloud/apps/richdocuments/lib/Service/CapabilitiesService.php line 73 OCA\Richdocuments\Service\CapabilitiesService->refetch() 16. /config/www/nextcloud/apps/richdocuments/lib/AppInfo/Application.php line 90 OCA\Richdocuments\Service\CapabilitiesService->getCapabilities() 17. /app/www/public/lib/private/AppFramework/Bootstrap/FunctionInjector.php line 45 OCA\Richdocuments\AppInfo\Application->OCA\Richdocuments\AppInfo\{closure}("*** sensitive parameters replaced ***") 18. /app/www/public/lib/private/AppFramework/Bootstrap/BootContext.php line 50 OC\AppFramework\Bootstrap\FunctionInjector->injectFn() 19. /config/www/nextcloud/apps/richdocuments/lib/AppInfo/Application.php line 89 OC\AppFramework\Bootstrap\BootContext->injectFn() 20. /app/www/public/lib/private/AppFramework/Bootstrap/Coordinator.php line 200 OCA\Richdocuments\AppInfo\Application->boot() 21. /app/www/public/lib/private/App/AppManager.php line 437 OC\AppFramework\Bootstrap\Coordinator->bootApp() 22. /app/www/public/lib/private/App/AppManager.php line 216 OC\App\AppManager->loadApp() 23. /app/www/public/lib/private/legacy/OC_App.php line 126 OC\App\AppManager->loadApps() 24. /app/www/public/ocs/v1.php line 58 OC_App::loadApps() 25. /app/www/public/ocs/v2.php line 23 require_once("/app/www/public/ocs/v1.php") GET /ocs/v2.php/apps/notifications/api/v2/notifications from 194.191.235.184 by oliver at 2023-09-04T13:05:01+02:00 I fixed my Nextcloud/Collabora integration issues with the guide I found here: https://help.nextcloud.com/t/nextcloud-collabora-integration/151879

Thanks @ScottAS2 There were only 20k left on the drive and i think that's why i couldn't delete the old datasets. I then deleted the complete TM-set and now everything is up and running again.

Great explanation, thanks a lot @ScottAS2 I wasn't aware that 2.5 TB is possible but no complaints with that setting from a dockers perspective 🙂 TM is reporting 1.32 TB available but it's still not running. Hopefully I don't have to delete files manually.....

This Docker is great and it is backing up one MBAir (256GB) one MBPro (512GB) and one iMac (1TB). It was running rock solid but now it caused an issue: I am using disk1 exclusively for this TM Docker and it filled up the drive by 100%. It's a 3TB drive and Docker run command is: -e 'VOLUME_SIZE_LIMIT'='3 T' I thought that TM is removing the oldest files. What is best practice?

I do not understand how to add the link that I am getting via the log. As soon as I am clicking on the link and basically linking unRIAD Dropbox to my Dropbox account I am getting another error (please see screenshot).

There was a issue with emby: https://emby.media/community/index.php?/topic/69848-feature-option-preventing-emby-from-deleting-media-files/ I have now revoked permission for all emby users to delete anything. A bug in emby was my first interpretation for the data loss, but horror crept in when I saw that some other files were missing....

Btw. since I am having installed 6.10.0-rc2 my server always comes up with a parity check....is it possible that this has something to do with the deletions?

Thanks Squid!!! One example: I had all episodes in season 1 of The Walking dead. Now only "The walking Dead-S01E06.mkv" is left. I might have made a mistake when I did a data rebuild a year ago or so....seems that I have to check my backup file by file?

Definitely in /mnt/user/iTunes and /mnt/user/Serien. I am afraid that there is more that I don‘t know yet.

Recently I discovered that a fair amount of TV shows were missing and I thought that EMBY was the culprit. Today I saw that music files have also been deleted. I am really don't trust my server anymore after running unRAID since more than 10 years. Diagnostics attached, thanks for any help or hint.

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='openHAB' --net='br0' --ip='192.168.178.22' --cpuset-cpus='5' --privileged=true -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -v '/etc/localtime':'/etc/localtime':'ro' -v '/mnt/user/system/appdata/openhab/conf/':'/openhab/conf':'rw' -v '/mnt/user/system/appdata/openhab/userdata/':'/openhab/userdata':'rw' --device=/dev/ttyACM0 --shm-size 2g 'openhab/openhab:latest-debian' /bin/chmod o+rw /dev/ttyACM0 && /entrypoint.sh 55c064827917c2b56ce5dbc5983f7d635623dec20f4aca7477e2b0fad4ef2e7c sh: /entrypoint.sh: No such file or directory ...doesn't like the command...

What does that mean please? Should I enter this into the Post Arguments box? /bin/chmod o+rw /dev/ttyACM0 && /entrypoint.sh

If you are using openhab/openhab:latest-debian as openHAB Repository you are getting that update automatically.

Unfortunately openHAB doesn‘t start when I am adding /bin/chmod o+rw /dev/ttyACM0 into the Post Arguments box....

There is on comment on Troubleshooting of OH3: docker exec \ -d \ openhab \ /bin/chmod o+rw /dev/ttyACM0 Is there any way to and that into the Docker template, or how to add ist myself? Maybe adding ist into the Post Arguments?

I was trying to get Collabora running as seperate Docker: I installed the container with default name (collabora), renamed the sample proxy conf, added the subdomain in SWAG and as CNAME at my DNS provider. SWAG log is showing: [cont-init.d] done. [services.d] starting services nginx: [emerg] "server" directive is not allowed here in /config/nginx/proxy-confs/collabora.subdomain.conf:3 Server ready nginx: [emerg] "server" directive is not allowed here in /config/nginx/proxy-confs/collabora.subdomain.conf:3 nginx: [emerg] "server" directive is not allowed here in /config/nginx/proxy-confs/collabora.subdomain.conf:3 nginx: [emerg] "server" directive is not allowed here in /config/nginx/proxy-confs/collabora.subdomain.conf:3 nginx: [emerg] "server" directive is not allowed here in /config/nginx/proxy-confs/collabora.subdomain.conf:3 ...... [cont-init.d] done. [services.d] starting services nginx: [emerg] "server" directive is not allowed here in /config/nginx/proxy-confs/collabora.subdomain.conf:3 Server ready nginx: [emerg] "server" directive is not allowed here in /config/nginx/proxy-confs/collabora.subdomain.conf:3 nginx: [emerg] "server" directive is not allowed here in /config/nginx/proxy-confs/collabora.subdomain.conf:3 nginx: [emerg] "server" directive is not allowed here in /config/nginx/proxy-confs/collabora.subdomain.conf:3 nginx: [emerg] "server" directive is not allowed here in /config/nginx/proxy-confs/collabora.subdomain.conf:3 ...... I thought that I followed @SpaceInvaderOne guide quite well but obviously I made a mistake.....

Thanks @saarg because I would need to set up a subdomain which is much more complex than using the build in Collabora (or Onlyoffice) app. I might be better off migrating to knex666 Nextcloud docker with full Onlyoffice integration based on Apache.

Sorry to bother again....is it realistic waiting for a fix of the integrated Collabora App? Thanks a lot.