Leftie

Experienced issues with Wireguard setup as well, after upgrading to latest version. Specifically, the docker log stated: vpn configuration file wg0.conf does not contain port on 'Endpoint' line This even though the output goes on to dump the contents of wg0.conf, showing that the port is indeed defined. Reverting to version 4.5.2-1-01 solved the issue.

It's been a very long while since any of my dockers wrote to that particular share, so I'm interested in learning what other things could cause this. Like I stated in the OP, the permissions looked OK when looking at the share via SSH. Since the problem showed up in connection with upgrading Unraid, I'm guessing there's been some changes to the passwd file or similar?

That did it! Thanks so much for your help, and for replying so quickly! Should I run this tool on the other shares as well, or is it only really needed in case of problems like I encountered?

One of my SMB shares (Video) can be accessed from my Windows computers, but only the first level of folders inside are visible. All these folders appear empty when browsing via SMB. All of my other shares seemingly work as they should. Browsing the shares via the Web GUI or via ssh, shows everything present as expected. I first noticed the problem after upgrading to Unraid 6.5.11 (I don't remember exactly which version I was running previously, but I was at least one or two minor versions behind). Fixes I've tried: Converting the entire array to XFS. I was previously running on ReiserFS (This is an old installation) File system checks (just with -nv parameters). I didn't see any obvious messages about corruption, so I've been reluctant to omit the -n argument, in case it could cause further problems. Checked file and folder permissions within the share. There are lots of combinations of permissions active in the different subfolders currently, but none of them display differently via SMB. Unexporting and re-exporting the share Sharing one of the disks directly (disk1). The same files and folders that are invisible through the normal share, are invisible here as well. I must admit I've run out of ideas... I've attached a diagnostic file. Hope you folks are able to point me in the right direction. tower-diagnostics-20221218-1044.zip

I've been trying to configure the CrashPlan Docker to replace my ISPs version of CrashPlanPro, but I'm beginning to suspect that this is not possible. I need to be able to set a different CrashPlan host to which the backup engine connects (i.e. my ISPs CrashPlanPro host), but this obviously cannot be done via the GUI. I'm afraid I haven't been able to find a config file setting for this either, but if any of you could enlighten me on this, it would be highly appreciated