rswafford

That looks perfect!! That's exactly the idea I was looking for, thank you so much for pointing out that I can share with it as well - I think I looked at it, and totally missed that I can actually share with it too. Thank you!!

Unsure what exactly you're getting at here. If ownCloud is on its own IP address, then it shouldn't matter if unraid does use 443 or not. It's a different IP than my Unraid server listens on. Just in case, I updated the docker config to map port 8443 (unused by anything else on Unraid at all) into the ownCloud docker. Still getting the same errors. I also spun up an instance of Nextcloud using the same br0 network, on 192.168.1.5, and it works perfectly fine. Really stumped here.

I'm assuming that's gotta be it... but here's my settings: I've got another docker (pihole) also running on the br0 network, and that doesn't seem to have any issues. It's configured for 192.168.1.2 as its IP -- and no, there's no other device on my network at 192.168.1.252 at this time. I also tried .15 for kicks as well.

For further information... looking at my Unifi router page, I can see the docker for ownCloud, or what I believe it to be, based on the MAC address - but its not assigning itself an IP Address, even though I have that filled in on the template. No IP == no connectivity... so why isn't the IP passing through?

I just installed this today, and if I have it configured to use br0 as the network, and a fixed/static IP, I'm seeing lots of errors in the log: Err:1 http://archive.ubuntu.com/ubuntu focal/main amd64 bsdmainutils amd64 11.1.2ubuntu3 Temporary failure resolving 'archive.ubuntu.com' Err:2 http://ppa.launchpad.net/ondrej/php/ubuntu focal/main amd64 libpcre2-16-0 amd64 10.40-1+ubuntu20.04.1+deb.sury.org+1 Temporary failure resolving 'ppa.launchpad.net' Err:3 http://ppa.launchpad.net/ondrej/php/ubuntu focal/main amd64 libpcre2-32-0 amd64 10.40-1+ubuntu20.04.1+deb.sury.org+1 Temporary failure resolving 'ppa.launchpad.net' Err:4 http://archive.ubuntu.com/ubuntu focal/main amd64 libuchardet0 amd64 0.0.6-3build1 Temporary failure resolving 'archive.ubuntu.com' Err:5 http://ppa.launchpad.net/ondrej/php/ubuntu focal/main amd64 libpcre2-posix3 amd64 10.40-1+ubuntu20.04.1+deb.sury.org+1 Temporary failure resolving 'ppa.launchpad.net' Err:6 http://archive.ubuntu.com/ubuntu focal/main amd64 groff-base amd64 1.22.4-4build1 Temporary failure resolving 'archive.ubuntu.com' Err:7 http://ppa.launchpad.net/ondrej/php/ubuntu focal/main amd64 libpcre2-dev amd64 10.40-1+ubuntu20.04.1+deb.sury.org+1 Temporary failure resolving 'ppa.launchpad.net' Err:8 http://archive.ubuntu.com/ubuntu focal/main amd64 libpipeline1 amd64 1.5.2-2build1 Temporary failure resolving 'archive.ubuntu.com' If I switch to use the bridge network and set a custom port number, then it goes through the whole setup process and I can land at the ownCloud install screen in the browser. Soon as I restart the container on br0, it tries to go through the whole setup process again with the same set of errors. What gives? What am I doing wrong, what should I look at?

Yeah... NextCloud would probably work, but given that I'm not hosting that right now and not sure I really need something that heavy I was hoping to find something more tailored to just this one use case. *sigh*.... why use a scalpel when a sledgehammer will do? LOL

I'm looking for suggestions for a self-hosted web application that I can run on my Unraid server and use it to share directories or files with specific friends and family. I've looked at a number of options like Seafile, ProjectSend, FileRun, FileShelter, etc - and they all fall short of what I'm looking to do. Mostly because they all require you to re-upload the file to the server so it goes in the app's appdata folder, or whatever - and it can't seem to just take a data directory, and let me say "share this folder path with friend Xyz". The files are already on an Unraid share. I just need to have a secure way to expose a specific directory to them to download one or all files in a folder. Does something like that exist?

More fiddling this morning, and I discovered that the circled checkbox on my Plex server was unchecked. As soon as I ticked it and tried another video, everything is HW transcoded. Not sure if this is a new setting, or got toggled off in a recent update, but anyone having problems with HW encoding should make sure both Hardware Acceleration AND Hardware Accelerated Video Encoding are toggled on:

Did you ever find a resolution for this? I have an i5-10400 CPU that up til recently (not sure when to be honest) had been running hardware transcodes flawlessly. I'm on unRAID 6.9.2 and the latest version of Plex docker from Plex's own repo. I cannot get hardware transcoding to work now to save my life.... and I don't see any sign of GPU hangs in the logs either.

Bumping this up to the top... I have an ASP.NET Core docker container that I'm trying to run, and as part of its process it spawns file watchers on a long list of subdirectories (it's a photo management app - Damselfly - so it watches for new photos to be added). I also have other dockers running for Radarr, Sonarr, Lidarr, Plex etc that also use file watchers to monitor for new media being added to their respective directories. I'm positive that R/S/L/P et al have far more than 128 inotify watchers being set up, given the size of each of those libraries. However, when I launch Damselfly, it'll set up watchers on a few of the subdirectories in my photo library, and eventually throw up a bunch of errors in its log like so: Exception creating filewatcher for /pictures/2007/2007-06-28: The configured user limit (128) on the number of inotify instances has been reached, or the per-process limit on the number of open file descriptors has been reached. Reading that, my first thought was to increase the inotify limit on Unraid. So I did that.. I've now got it up to 4,000,000, and can see that both through the console as well as the Tips and Tweaks plugin. The numbers match. And yet, that docker container still complains about a 128 inotify max. To make it even more confusing, I just tried installing another docker (also ASP.NET Core it appears) for Kavita - if Damselfly is running before I start the Kavita docker, Kavita hits the same exact error and refuses to start. If I launch Kavita first, it runs without incident. I have rebooted the whole server, I have 64 GB of RAM, so memory isn't an issue... what else can I do to force these docker containers to recognize the correct inotify watch limit?

Weird... I started with the one Sycotix provided in Github... I'll try again from scratch maybe.

Got this set up, ran through the config guide, and when I try to access via local ip (http://192.168.1.xxx:9091), my browser just gives me the generic Chrome error "This site can't be reached". In the Authelia container logs, I see: What'd I miss?

No, I wanted to consume the directory directly via a folder mount. I was confused by the note and wanted to make sure there wasn't anything funky with the Docker on unRAID setup that would make it appear as an NFS mount somehow. Thanks!

Completely new to unRAID... planning to migrate from Windows/Docker Desktop in the near future. In the FAQs you have listed a note about inotify not working on NFS shares -- does that apply to the way the data volume is mounted for this app, or all instances of paperless-ng running via Docker containers? I've been experimenting with Paperless for a couple of weeks now in a sandbox, and plan to roll it out on my unRAID... but I had hoped the inotify folder watcher would just work since unRAID is Linux at its core (I got bit last year trying to set it up on Windows Docker because inotify doesn't work on Windows folders at all - volumes or not).