Opus44

Title says it all. I need four.

read/write for owner/group/other translates to 666. Looks like you need execute permissions on at least the owner and the group along with read and write. Go to the terminal, and issue the following commands: cd /mnt/Data chmod -R 770 ./nextcloud I'm surprised the dynamix file manager doesn't offer a setting to toggle the execute permission.

Sorry to say you will have to collect the diagnostics files on an updated system. Before doing that, I have a few questions/suggestions. Was 6.10.3 your initial install of UNRAID? Are you stopping all your docker containers, vms, and plugins before doing the upgrade? SpaceInvader One has an excellent tutorial on doing a clean upgrade.

Quick observation: all the log entries, and all the diagnostic files have Jan 4 2022 timestamps. Not sure what if any problems that might cause.

Welcome aboard. Post pictures of Velo. It sounds awesome.

Clearing the browser cache fixed all of scenario two and the sign-in problem with scenario one. Thanks so much for solving this. I spent way too much time agonizing over this.

Yes. that is clear and what I expected. Only thing I am baffled by with result one is not being able to sign in. But what you say makes sense and I will flush the cache and see if that clears things up for that scenario. I totally don't understand the problems with scenario two. It makes me wonder if there is a problem with the SSL certificate in the /boot/... folder. Also curious as to why there are two. Is it because I renamed the UNRAID server after setting it up?

Scenario One Conditions - myServers plugin not installed - use SSL/TSL no - two SSL certs in /boot/config/ssl/certs root@rocky:/boot/config/ssl/certs# ls -la -rw------- 1 root root 2851 Sep 15 15:51 rocky_unraid_bundle.pem -rw------- 1 root root 2884 Sep 14 15:56 unraid-server_unraid_bundle.pem - Self-signed or user-provided certificate: /boot/config/ssl/certs/rocky_unraid_bundle.pem - Certificate URL: rocky.local - Certificate issuer: O = Self-signed, OU = unRAID, CN = rocky.local - Certificate expiration: Sun 12 Sep 2032 03:51:06 PM CDT - CA-signed certificate file: Not present local access results: http://192.168.X.XX/ works- signed in "not secure" http://rocky.local/ displays sign-in screen but refuses signin as root https://192.168.X.XX/ site can't be reached https://rocky.local/ site can't be reached Scenario Two: - use SSL/TSL yes - everything else set the same local access results : http://192.168.X.XX/ (redirects to https://192.168.X.XX/) does not redirect but does sign-in https://192.168.X.XX/ (uses certificate rocky_unraid_bundle.pem ) redirects to http and signs in http://rocky.local/ (redirects to https://rocky.local/) does not redirect but does sign-in https://rocky.local/ (uses certificate rocky_unraid_bundle.pem ) redirects to http and signs in I also have scenarios with the myservers plugin installed while using/not using remote-access that do not behave properly. But before delving into them, I'd like these two scenarios resolved. Let's keep thing simple. rocky-diagnostics-20221104-0835.zip

Unfortunately I didn't take diags at the time the problem happened. My oversight. Sorry. If it happens again I shall be more diligent. Thanks for responding.

rebooting brings the shares back, but it would be nice to have more confidence with rsync and user-scripts.

I've a noobie to UNRAID and I've been setting up user-scripts to run rsync commands. While testing them, I ran into a problem that seems to have removed all my shares. Shares were defined days ago and I have been using them via windows, unraid user scripts, and the unraid terminal.

2 Unraid servers. Brought the first one up three weeks ago and only recently acquired an Unraid OS Plus key. The second one I am configuring now. It will be very limited in scope, just used for offsite backup. Could probably just get by with s bare linux box and some rsync commands, but think I will find reasons to grow its functionality as I get more familar with Unraid.