GuyWithAQuestion

Awesome. Thanks for keeping us updated and taking the time to post a reply, SpencerJ! And thank you, T0rqueWr3nch, for confirming and your insight as well. I appreciate both responses.

Apologies if this is a duplicate post to what ncohafmuta put up here, but I think we are discussing separate topics. CVE-2024-21626 was published a few days ago. I'm currently running 6.12.6 and running 'docker version' from command line reveals docker engine version 20.10.24 and runc version 1.1.5. Is the best course of action is to disable docker updates until docker is updated? Or am I misunderstanding and this is this not affecting unRAID? Thank you.

I’m case it helps, I use the linuxserver/ nextcloud docker container. Though I don’t recall the version number I installed (it’s been a few years)

It didn't fix my issue. Before I posted here, this was one of the things I tried doing. I ran both (under the Tools menu) prior to posting here: Docker Safe New Perms & New Permissions

Nextcloud is working the way I thought it might; I didn't really have SAMBA access to it (never paid attention to it). I only used the nextcloud docker to sync between machines (and probably only ever used the console to look at files there). I didn't have read/ write permissions, so turned it on for my user. But interestingly enough, even once I've done that.... it remains the same as what you saw above. drwxrwx--- 1 nobody users 184 Sep 21 18:07 nextcloud/ drwxrwxrwx 1 nobody users 48 Jul 6 2021 system/ would you recommend running chown 777 on that directory as well?

GASP. That was it! Thank you thank you thank you both for stepping through this with me and thank you for your great catch and instructions, JorgeB! Went from this: root@bryNAS:~# ls -la /mnt/user total 40 drwx------ 1 nobody users 206 Sep 21 16:46 ./ drwxr-xr-x 13 root root 260 Sep 21 16:36 ../ to this... root@bryNAS:~# ls -la /mnt/user total 40 drwxrwxrwx 1 nobody users 206 Sep 21 16:46 ./ drwxr-xr-x 13 root root 260 Sep 21 17:19 ../ I too am mystified by it working in 6.9 but not 6.10. Again, thank you both. I'll of course mark the correct solution and leave it up for anyone else who might be wandering through the internet with the same issue to hopefully find their solution. Now it's time to explore what this 6.10.3 unRAID server can do

Thank you for your ongoing help, all. JorgeB, here's the output you requested To compare: This is 6.9.2. (6.10.3 is below) root@bryNAS:~# ls -la /mnt/user total 40 drwx------ 1 nobody users 206 Sep 21 09:48 ./ drwxr-xr-x 13 root root 260 Sep 21 09:38 ../ drwxrwxrwx 1 nobody users 6 May 12 2021 .Trash-99/ drwxrwxrwx 1 nobody users 4096 Dec 5 2021 Backups/ drwxrwxrwx 1 nobody users 14 Aug 12 22:31 Downloads/ drwxrwxrwx 1 nobody users 36 Aug 12 22:31 Media/ drwxrwxrwx 1 nobody users 6 May 12 2021 Sync/ drwxrwxrwx 1 nobody users 48 Jul 7 2021 Time\ Machine\ unRAID/ drwxrwxrwx 1 nobody users 28 Aug 26 2021 Téléchargements/ drwxrwxrwx 1 nobody users 1018 Jul 27 16:50 appdata/ -rw-r--r-- 1 nobody users 619 Mar 15 2020 cert.pem -rw------- 1 nobody users 4089 Mar 15 2020 config.xml -rw------- 1 nobody users 33 Mar 15 2020 csrftokens.txt drwxrwxrwx 1 nobody users 216 Jan 10 2022 domains/ -rw-r--r-- 1 nobody users 623 Mar 15 2020 https-cert.pem -rw------- 1 nobody users 288 Mar 15 2020 https-key.pem drwxrwxrwx 1 nobody users 6 May 12 2021 index-v0.14.0.db/ drwxrwxrwx 1 nobody users 4096 Dec 25 2021 isos/ -rw------- 1 nobody users 288 Mar 15 2020 key.pem drwxrwx--- 1 nobody users 166 Sep 6 2021 nextcloud/ drwxrwxrwx 1 nobody users 48 Jul 6 2021 system/ root@bryNAS:~# This is 6.10.3 root@bryNAS:~# ls -la /mnt/user total 40 drwx------ 1 nobody users 206 Sep 21 09:48 ./ drwxr-xr-x 13 root root 260 Sep 21 15:25 ../ drwxrwxrwx 1 nobody users 6 May 12 2021 .Trash-99/ drwxrwxrwx 1 nobody users 4096 Dec 5 2021 Backups/ drwxrwxrwx 1 nobody users 14 Aug 12 22:31 Downloads/ drwxrwxrwx 1 nobody users 36 Aug 12 22:31 Media/ drwxrwxrwx 1 nobody users 6 May 12 2021 Sync/ drwxrwxrwx 1 nobody users 48 Jul 7 2021 Time\ Machine\ unRAID/ drwxrwxrwx 1 nobody users 28 Aug 26 2021 Téléchargements/ drwxrwxrwx 1 nobody users 1018 Jul 27 16:50 appdata/ -rw-r--r-- 1 nobody users 619 Mar 15 2020 cert.pem -rw------- 1 nobody users 4089 Mar 15 2020 config.xml -rw------- 1 nobody users 33 Mar 15 2020 csrftokens.txt drwxrwxrwx 1 nobody users 216 Jan 10 2022 domains/ -rw-r--r-- 1 nobody users 623 Mar 15 2020 https-cert.pem -rw------- 1 nobody users 288 Mar 15 2020 https-key.pem drwxrwxrwx 1 nobody users 6 May 12 2021 index-v0.14.0.db/ drwxrwxrwx 1 nobody users 4096 Dec 25 2021 isos/ -rw------- 1 nobody users 288 Mar 15 2020 key.pem drwxrwx--- 1 nobody users 166 Sep 6 2021 nextcloud/ drwxrwxrwx 1 nobody users 48 Jul 6 2021 system/ root@bryNAS:~# Frank1940, here's what I have for you: C:\Users\bryan>net use * /delete You have these remote connections: M: \\10.22.22.4\Media N: \\10.22.22.4\Backups Z: \\10.22.22.4\Downloads Continuing will cancel the connections. Do you want to continue this operation? (Y/N) [N]: Y The command completed successfully. C:\Users\bryan> I then go through explorer on Windows 10 and put in the server address as \\10.22.22.4 Which brings up all the shares that are 'exported'; mainly I've been playing around with Backups and Downloads (and then Flash when it was exported as SMB as we previously discussed, which was accessible). Now, trying to select to go into Backups I get this: I double checked my WORKGROUP settings and it appears to be correct: In addition, between all of these attempts to get in, I've rebooted both my unRAID server as well as my Windows machine, re-ran the "net use * /delete" command, and lastly have tried toggling between Public and Private (each with the net use command as well as reboots for good measure). Scratching my head over this one.

I cleared the credentials using the following steps: - Open the start menu, in the search bar type: control panel - You will see an application called control panel, select this item. - In the control panel window, open the Credential Manager control panel. - In the Credential Manager control panel, click on Windows Credentials. - From there you can check/edit/delete your saved network credentials. Then rebooted my windows machine. and I tried it with the shares set to both "Public" and "Private" (with user my username having read/ write permissions granted when set to private; I even tried the user 'root'); all the same result unfortunately indicating that I don't have access. Similar results on my Mac. When I subsequently downgrade to 6.9.2, it all comes back up and I have access again without making any changes to the shares.

No. I have an actual user account that has read/ write permissions on the shares. I'm not using root other than to log into the web interface.

Thanks for your patience. I returned home today and tried exporting the flash as "public". While I'm upgraded to 10.6.3, I CAN access the flash drive as a SMB share (can see the files contained on it), but the other shares remain inaccessible (get the same error as above "You do not have permission to access this server"); and that remains true even if I go to Shares --> <share name> --> SMB Security Settings --> and change Security from "private" to "public". I think that's good information to learn. I just don't know what it means in terms of next steps.

Ahhhhh... very good, very good. I think I understand a little bit more about it now. I mistakenly thought that would give me SAMBA access to my flash drive itself and didn't do it correctly then! Thanks for the walk through. So what I understand here now is that if I set it to public, then export it and reload it on another drive it will clear out anything that I have set to private settings and make them public once I use that new drive? I will try this!! Unfortunately, there will be a few days delay as I don't have physical access to my server right away, but I'm hopeful!! Thank you! And, not using an Active Directory Service.

Thank you. Tried it with a newly installed USB and brought over the other USB configuration. No luck with that. I also did temporarily try a brand new install to see what would happen and didn't go too far since it would require me to reset all the parity, cache, data drives (I got in far just enough to see that this would be a very troublesome). I think I may be headed towards a complete system redo at some point. It seems a little beyond a permissions issue at the heart of the matter if I turn the shares to Public and still can't access the drives. Thank you very much for your insight so far!

Thank you Jorge & Frank for the replies and suggestions. JorgeB, did as you suggested. I removed any of the extra SMB settings (the only thing that shows up in there I think is populated by the unassigned devices, and it comes back if I delete it. I pasted it at the bottom of my post). I had and did a safe mode reboot. The issue persists. As far as the trial key, you mean just use a separate USB with a fresh install of unRAID on it? I did put it on another USB, same result. In addition, I tried upgrading to the 6.11.rc-5, unfortunately, that’s giving a similar result (cannot access shares due to permissions). Frank1940, I’ve tried accessing through a bare metal Mac and PC. Also have tried through the VMs I have loaded on there. Similar permissions issues. The disconnects I have only tried on the Mac (There’s a “disconnect” button when working on a network that you then can sign back in as guest or another user). Tried what you mentioned with Windows, similar result (just being told cannot connect to network drives). I have changed the share settings from private to public, but still the issue Is present. These are really good suggestions, so thank you for them. This is what comes back in the SMB settings, but I suspect that it should be there: #unassigned_devices_start #Unassigned devices share includes include = /tmp/unassigned.devices/smb-settings.conf #unassigned_devices_end

Now I'm curious as to if this is a "just me" problem as there have been a lot of views, but no responses? In which case, eventually the solution is just to start redo my server from scratch (e.g. back up everything I can and then do a fresh install). Clearly the issue must be something with the flux capacitor that the unRAID parity drives use.

Afternoon all, Sorry if this is addressed in one of the other postings about permissions, but I've tried reading through those and troubleshooting, but am still stuck. I've upgraded from 6.9.2. to 6.10.3. As far as I can tell, everything as far as Dockers (PLEX, PiHole, etc) works fine. It's just accessing the files themselves through the server on the network (using SMB either through Mac OS 12.4 Monterey or Windows 10). I disconnect as the user, reconnect, same error. Each time I get "You do not have permissions to access this server". I've stopped and restarted SMB. I've run Tools > Docker Safe New Permissions. I've run Tools > New Permissions. If I downgrade to 6.9.2, I'm back in business and everything works fine, but I'd sure like to use some of the 6.10.x features. As far as I can tell my directories/ files have the correct owners/ permissions... but I am at a loss. Attached are a few screenshots and diagnostic files (Tools > Diagnostics). Thank you in advance.

1) Being able to expand my array with different size drives 2) Snapshots I'm a new user who's coming from FreeNAS. I liked FreeNAS for its ability to store my data. However, when I wanted to start using it for other things (VMs, Plex Server, PiHole, VPN server, etc) it was waaaaaaaay easier to setup, manage, and learn about (Spaceinvader One videos and community support!!!) with unRAID. unRAID is well worth the cost.