tris203

It appears to be array related, as if i copy from the Isos share (prefer:cache) it is a solid 110MB copy down

Hi guys I am having issues with intermitment slow share speeds. For example copying a 1GB file down from the array to a local SSD (1gb network), it starts at 50MB/s then drops down to 350kB/s and eventually times out This is causing issues with Plex and Paperless and anything else that uses the array for storage. Attached is a diagnostics, any pointers to get started? Array itself seems healthy, and disks arent reporting any issues unraid-diagnostics-20221203-1731.zip

It does. Running in green

Sorry, just a regular SMB share called "General" which stores photos, documents etc. I havae also tried creating a new file in there. Nothing logged as a side note, I also have the openfiles plugin, and opening files shows records in there but not in the file activity plugin

I was opening files from my general share and nothing was being logged

I cant get this to log any information. The process seemingly starts, but now rows are listed in the file activity section I have checked the syslog and cant see any errors about inotifywatches. Mar 6 23:13:43 Unraid ool www[4853]: /usr/local/emhttp/plugins/file.activity/scripts/rc.file.activity 'start' Mar 6 23:13:43 Unraid file.activity: Starting File Activity I can see the process running root@Unraid:~# ps aux | grep inotify root 5371 0.0 0.0 2588 780 ? S 21:46 0:00 inotifywait -q /boot/changes.txt -e move_self,delete_self,modify root 8363 1.6 0.0 3044 2216 ? D 23:13 0:00 inotifywait -mrqs -e open,attrib,move,create,delete,modify --excludei (appdata|syslogs) --timefmt %b %d %H:%M:%S --format %T %e => %w%f --fromfile /tmp/file.activity/file.activity.disks root 9147 0.0 0.0 3904 1944 pts/2 S+ 23:14 0:00 grep inotify Diags attached unraid-diagnostics-20220306-2312.zip

I fixed it for anybody wondering. The issue (stupid me) was that the docker config was set to not enable access to host networks for containers. So by enabling this, that allowed me to run the docker on its own IP on the genuine port 443 Then i could add a internal dns entry for nextcloud.mydomain.com to point internally to the internal IP There is currently a certificate error, but I think that can be fixed fairly easily

Having an interesting one, so i have the docker installed and all is working fine with the connectivity in Bridge mode (running on port 444). This is then forwarded with NGINX to nextcloud.mydomain.com on port 443 With the exception that all traffic goes out to the internet and back in again. EG setting up a laptop/mobile where I want the connection to be to nextcloud.mydomain.com so that it works outside of the LAN the uploads goes out the internet and back in again, this isnt ideal for speed or bandwidth usage. I tried setting up a DNS entry to point nextcloud.mydomain.com to the unraid server internal IP, but that fails due to the port mismatch (apps configured to use 443, service running on 444, and 443 being the unraid console). I have tried reconfiguring the docker to use a custom network so it has its own IP and can run fully on 443 with no port mapping but that doesnt seem to work (the next cloud service just fails with an internal server error. Am I over complicating this?