6.9.2 --> 6.10.3; "You do not have permissions to access this server"

[GuyWithAQuestion]

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.
 

 

Edited September 21, 2022 by GuyWithAQuestion
log files not needed

[GuyWithAQuestion]

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.

[JorgeB]

12 hours ago, GuyWithAQuestion said:

Now I'm curious as to if this is a "just me" problem

Don't remember seeing a similar issue, and certainly not a common problem, temporarily remove any extra SMB settings if you have them and/or boot in safe mode, if issue persists boot with v6.10.3 in a trial key to see if it's config related. 

[Frank1940]

Try changing one of the shares from 'Private' to 'Public' and see if you can gain access. 

 

 

 

On 9/10/2022 at 5:27 PM, GuyWithAQuestion said:

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).

Are both the MacOS and Win10 running on bare metal or are you using a VM's?

 

On 9/10/2022 at 5:27 PM, GuyWithAQuestion said:

I disconnect as the user, reconnect, same error.

How are you doing this 'disconnect'?  (It is not a simple task with WIN10.  As I recall, it involves the use of the command line.  Plus the WIN10 client only allows one connection to each server. See more info on how do: this quote is from this post---    https://forums.unraid.net/topic/25064-user-share-problem/?tab=comments#comment-228392      )

 

Quote

To get above to work, you would close any windows that might have a previous connection to the first public share, then open a command window and type "net use * /delete".  That command closes all current server connections. 

 

[GuyWithAQuestion]

 

 

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

 

[JorgeB]

5 hours ago, GuyWithAQuestion said:

As far as the trial key, you mean just use a separate USB with a fresh install of unRAID on it?

Yes, use a new Unraid install, you don't need to assign devices or start the array, just export the flash drive and see if you can access it.

[GuyWithAQuestion]

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!

[Frank1940]

@GuyWithAQuestion, did you try this one:

12 hours ago, JorgeB said:

Yes, use a new Unraid install, you don't need to assign devices or start the array, just export the flash drive and see if you can access it.

To share/export the flash drive, you go to   Main  and Left- Click on    Flash   then under   SMB Security Setting   turn on 'Export:' and make sure the security is set to 'Public'.  

 

You don't need to do this at all!

17 minutes ago, GuyWithAQuestion said:

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 would be surprised if just sharing out the Flash Drive via SMB on a virgin install gave an issue.  If that were the case, we would have many, many folks posting up with issues...

 

[Frank1940]

Are you using an Active Directory service?

[GuyWithAQuestion]

20 minutes ago, Frank1940 said:

 

To share/export the flash drive, you go to   Main  and Left- Click on    Flash   then under   SMB Security Setting   turn on 'Export:' and make sure the security is set to 'Public'.

 

 

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.

[Frank1940]

No---  What we are expecting to export the flash (or boot) drive as a SMB share.  Then you access the server via your file browser.  You should see 'flash' as a SMB share.   (With WIN10, in File Explorer, one would type   \\ip.address    on the address bar.  Not sure what the command is with MacOS as I do not have a Mac.)

 

@JorgeB suggested this because it is a very quick way to see to test out SMB access without requiring that a working array of data disks be set up.   If another computer (besides your Unraid Box), you will also have a new IP address as it will have a different MAC address for the NIC.  (Laptops are ideal for this type of testing setup.) 

 

I  just verified that the flash share will be exported when the array is shutdown.     

[GuyWithAQuestion]

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.

[Frank1940]

You are not trying to log as the user---   root   ---are you?

[GuyWithAQuestion]

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.

[JorgeB]

On your Windows PC got to control panel - credentials and delete all stored credentials for the Unraid server, then reboot Windows and try again.

[GuyWithAQuestion]

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.

 

 

[JorgeB]

Upgrade back to v6.10.3 and post the output of:

 

ls -la /mnt/user

 

[Frank1940]

2 hours ago, GuyWithAQuestion said:

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.

 

Please understand that there can be only one client login to each server under Windows.  Once you are logged in, it takes a command prompt window using Administrative privileges to log that user out.  This is the command that you use:

net use * /delete

One more important thing is that the Windows Credentials are automatically used to log a user onto SMB.  That is why you were told to delete them using Credential Manager.  These are often stored the first time you log onto a server.  So you have to check to see what is there when you have access issues. 

 

Try using    \\Server-Name    in the Address panel of Windows Explorer  (Windows 10's File Manager)  and see if you get an error message from that.  What should be displayed is all of the SMB Shares that you have exported as folders.  It probably will look something like this:

I have circled where to put the Server-Name.   Appearance may vary depending on the Windows Explorer View settings...

 

One important thing to realize is that most SMB error messages are not really very useful/informative about the actual problem

 

Also verify that you have your server setup to become the Local Master Browser.    Settings    >>>  Network Services   >>>   SMB    >>>  Workgroup Settings    

[GuyWithAQuestion]

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.

[Frank1940]

On that Win10 PC, open up the following and lets see what your settings are:

Note that the network profile is set to private.  Make sure your computer is set to private and the "Turn on network discovery" radio button is selected.  If the current profile is not "Private",  see here for how to switch it:

 

      https://www.groovypost.com/howto/change-network-profile-public-private-windows-10/

 

to connect with a Public or guest account, I believe you have to make changes here:

 

[JorgeB]

53 minutes ago, GuyWithAQuestion said:

drwx------  1 nobody users  206 Sep 21 09:48 ./

/mnt/user permissions are wrong, don't ask me why they work with v6.9, but they are still wrong, type

chmod 777 /mnt/user

reboot and try again.

[Frank1940]

20 minutes ago, JorgeB said:

/mnt/user permissions are wrong, don't ask me why they work with v6.9, but they are still wrong, type

chmod 777 /mnt/user

reboot and try again.

@JorgeB, GREAT catch!  IF I remember how permissions work on directories that should fix it.

 

As to the question why 6.9.2 worked when 6.10.3:

 

• 6.9.2 has   samba: verson 4.12.14
• 6.10.3 has   samba: version 4.15.7

 

I would guess that one of the CVE that were incorporated had something to do with tightening up the access to the file system.  (I never have quite figured out how the permissions applied to the various SMB users work with the underlying Linux permissions.)

Edited September 21, 2022 by Frank1940

[kizer]

I just triple checked. That's exactly how mine sits.  Nice Catch

 

ls -ls

0 drwxrwxrwx  1 nobody users 173 Sep 20 11:14 user/

 

 

[GuyWithAQuestion]

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

 

[Frank1940]

Does anyone have any thoughts on how the permissions on just that one directory got changed?

 

@GuyWithAQuestion, double check that NextCloud is working properly as the permissions on that share are a bit wonky from what we would normally expect. 
 

drwxrwx--- 1 nobody users 166 Sep 6 2021 nextcloud/
drwxrwxrwx 1 nobody users 48 Jul 6 2021 system/