Godvader

Hi everyone, great insight so far. I am setting up a very similar system as the OP so I didn't want to create a duplicate post. I have an nvme only NAS with 4 slots, 2 of which is currently populated. Similar to OP. My question: If I create a pool with 2 slots right now, what happens if I want to add another ssd to that pool? I plan to add another one soon so if I have to delete everything and create a new pool once I have another ssd, it feels like I will be better off buying that ssd now and creating a 3 slot pool once it arrives. Correct? This is my first time setting up an NVME only Unraid and I figured out some stuff thanks to this post so thank you all!

I am connecting to the Unraid server remotely. Not even in the same country I have a windows machine on the same network as the Unraid server and that can connect to the SMB shares without a problem. I tried to remotely connecting through Wireguard both on an iPhone and a Mac. I tried both private and public shares. I am giving the right credentials to access the smb shares as it was working before the update.

Hi all, I was trying to update the community applications plugin yesterday but got the warning that my Unraid version wasn't supported anymore. I then updated from 6.10.x to 6.12.10 and this broke the SMB access over Wireguard. I keep getting "can't connect to server" error. I set up the built in wireguard following the guide in the docs. This was my initial configuration: Remote access to server Use NAT set to Yes Host access to custom networks set to disabled No static routes on my router This is the basic configuration following the guide in the docs which used to allow me to access the shares through SMB on the old Unraid version. After the update: I can access the server GUI through wireguard I can access SMB shares locally I can't access the SMB shares remotely through Wireguard This 8 months old post on Reddit talks about the same issue, they apparently fixed it by rolling back to 6.11.x ... I think this post on the Unraid forums is about the same issue as well. So I searched around and found these solutions to be recommended: Follow the "complex network" approach mentioned in the setup guide. It makes no sense to me since my network didn't change at all and it used to work on older version of Unraid... I tried to this and quickly found out I can't set static routes in my router so that is impossible. Change macvlan to ipvlan. Didn't seem to change anything? I am lost beyond this, any help is welcome!

FYI: I started having permission issues after upgrading to Unraid 6.11. sudo chown -R nobody:users /mnt/user/<output directory> I solved it by running the above command. Change the <output directory> to your own /output/ directory.

So I guess I have to ask for help here. I am having the infamous not being able to write to private share issue. I can access all of the shares just fine but I can't write to private shares. I can write to public shares. What I tried so far: I have matched the username and passwords between windows 10 and unraid. tried the use net * /delete command restarted win machine couple of times installed the loclal master plugin and made sure the unraid server is the local master removed all credentials from win10 restarted win machine again I can write to private shares from macOS without any issues.