RogerTheBannister

Members
  • Posts

    7
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

RogerTheBannister's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Scenario: I want to create a shared folder on my Windows PC that can be accessed by Unraid (for example, moving files between PC and server with Krusader). However I'd like that folder not to be accessed by other PCs on the network. I can create the share and mount it, but it seems like it will only work so long as when making the folder shared in Windows, read permissions are given to "Everyone". This of course means any other PCs on the network can find and access the folder. Is there a way to get around this? Note, Password Protected Sharing is disabled on my PC (which I believe is a requirement for the remote share to work) and I also do not log in to Windows with a password.
  2. I guess both. I was wanting to access my server remotely (do stuff via the webUI and transfer to/from a shared folder) and run apps like deluge through a VPN connection. I believe that was the guide I was initially going through until I saw the words "port foward" on the second to last step and just cancelled what I was doing. I should have paid more attention to the link in the first paragraph - "If you need access to Docker containers, network drives, or other devices on your network, you'll want to setup a VPN instead". Specifically the part on Wireguard, as at a glance that sounds like what I should be doing. It's a lot of reading, so I'll work my way through it later on. https://wiki.unraid.net/Manual/Security#WireGuard Yes, this seems to be working well now. At least with deluge I can see my connection is going through a VPN. I actually forgot what I was doing here with my initial post, now I remember I had another issue unrelated to VPNs. I was following a guide to setting up Radarr / Sonarr but had to put it on hold when I got to the part on adding an indexer. I didn't realise indexer sites were some whole other world of secret clubs you have to be invited to, and paid memberships, so that's another project for another time, and a completely different topic!
  3. Well then. I did say it would be really obvious! I'll mark this as solved, but any thoughts on the port forwarding part of my post?
  4. This will probably be a really obvious solution, but I'm easily confused when it comes to network stuff. New to NAS / UnRAID. I use the Mullvad Windows app as a VPN for desktop browsing. I've noticed when it is enabled, I'm unable to access any part of my NAS - shares, webui, dockers etc. Is there something I need to change within UnRAID? I want to avoid making a "permanent" change in Windows as I frequently toggle the VPN on and off, and don't want to have to change network settings every time. I may have this wrong, but reading around, I got the impression that I could set my desktop up to connect through the NAS's own VPN. I wouldn't want this, as I currently don't plan to have the NAS running 24/7. Related: I have wanted to run a few things such as remote access, LANCache, radarr/sonarr/deluge but had to stop short when I discovered they all require port forwarding. This is not possible with my ISP/router. I heard that using a VPN is a way to get around this? Is this true, or is there no way to get around port forwarding? I previously followed though a tutorial in setting up deluge / privoxy / radarr and part of that was configuring a wireguard file which I got though my Mullvad account. I was able to confirm this was working by running the command curl https://am.i.mullvad.net/connected through either the deluge or privoxy container, where it correctly outputs my VPN'd IP. So I got that part working at least.
  5. This did the trick, thanks. Everything seems to be as it should now. I did try the New Permissions tool first, which I see just runs the same command but with a different combination of letters. My head hurts a bit trying to decypher them, but long story short, it didn't work. To be clear, the folder in question was made manually before I had even started installing any dockers. Going though my list of dockers, there are a couple which have the UMASK key, which is set to 000. They do not have any direct association with the folder, except one of them is Krusader. If I had used Krusader to create the folder, could this have been the cause? What is the difference between 000 and 007? In addition, all the dockers UIDs and GIDs are 99 and 100 respecively, except again for Krusader, which are both set to 0. I'm starting to suspect something here... I remember changing these to 0 after looking up how to fix some other issue which I have now forgotten.
  6. Just learning my way around the terminal now. Ok, so most folders are showing: drwxrwxrwx 1 nobody users with the problem folder showing: dr-xr-xr-x 1 nobody users If I look inside the problem folder, its contents are all over the place too: drwxrwxrwx 1 myname users 4096 Jan 25 13:04 Folder 1/ drwxrwxrwx 1 root root 94208 Jan 25 13:03 Folder 2/ drwxr-xr-x 1 nobody users 183 Jan 25 01:35 Folder 3/ drwxr-xr-x 1 nobody users 162 Jan 24 17:31 Folder 4/ drwxr-xr-x 1 nobody users 48 Jan 24 18:24 Folder 5/ In the example above, the folders 3 4 and 5 were created automatically by a docker app. Folder 1 was copied over from Windows - has it inhereted permissions from Windows? I could use that New Permissions feature, but like you say I'd like to figure out what's going wrong. Pretty sure I would have made the folder from within Windows after setting up the share. I have also been using Krusader.
  7. New to unRAID and linux-like things in general, been setting everything up over the last few days and learning the ropes. One issue that has come up is with one of the SMB shares I've set up. Let's say we have the folder Media, with the subfolders Music and Video. The share is set to export, private, with a user (myself) given read/write access. In Windows (10), I can access each of the folders using the appropriate name/password, can read/write into the Music and Video folders, but cannot write to the parent Media folder. I've tried setting up and logging in under a different name too. even stranger, I have another share with the exact same setup with the only difference being the share name. This one lets me write to the parent folder just fine. [Edit] As time has gone on and I've installed more things and added more folders, this issue has come up again now with other subfolders within the Media folder also being read-only.