You need to forward the https port and use https, not http. You could enable HTTP admin access, but that's a really bad idea when you've forwarded port 80. I recommend you not forward port 80 at all and use https for share access, too. The standard https port is 443, but you can use an alternate one, too, which may cut down on anyone snooping out your NAS. Where you specify the alternate port the NAS will use depends on whether you are still on RAIDar4.2.x or have moved to 6.x on your Ultra. The only real eason you'd need to use the NAS alternate port is if your router does not allow you to specify different LAN and WAN ports for forwarding. Otherwise, just choose an alternate incoming port in the router. If you do use an alternate port, you have to add a colon and the port to the end of the URL.
And even after I added portforwarding for https port 443 it wont work to access /admin remotely. Should I choose TCP or TCP/UDP ? Still its only /shares that I can acess
cifs, ftp, http/s is shared in settings All users are in the group "users"
I then disable http on port 80 forwarding so then its not browsable at all
Using https on 443 is not working
Not even if I write IP:443
Tried another port also 5656, not working
Locally if I share folders using cifs, all folders are visible and accessable with admin passw
That might be ok, but how do I restrict different other users to access some folders ?
I shared everything, cifs, ftp, http/s to test
FTP works great, can access all folders
But not via https
What about qouta ?
Does 0 mean infinite space or zero space ?
Why set a qouta anyway ?
You can set qouta on both groups and users, makes me confused...
And even after I added portforwarding for https port 443 it wont work to access /admin remotely. Should I choose TCP or TCP/UDP ? Still its only /shares that I can acess
HTTPS uses TCP, so that is enough. Then use https://wan-ip-address/admin from an external place (more likely using a ddns name than the wan ip address).
Does http://canyouseeme.org/ show the port as open? Sometimes ISPs block ports. Your router might also reserve 443 for it's own remote management. So maybe also configure a different destination port (say 50000) to also forward to the NAS 443 destination port, and try https://wan-ip-address:50000/admin
Great! 50000 to 443 works But I get browser warnings about unsafe site and https is crossed over.
About users and groups I created myself as a user in same group as all others, Group named users. When I login using https://wan-ip-address:50000/shares I see same as the admin sees ? Isnt it possible to configure so some users cant see/access certain folders ? And where are the home folders, I can not see them.
Whats the point making a group when the only thing I can set is quota ? Is 0 the same as unlimited ?
Great! 50000 to 443 works But I get browser warnings about unsafe site and https is crossed over.
That is expected - that happens because the NAS uses a self-signed certificate, so authentication isn't possible. It is possible to add that certificate to your PC's root store (details depend on the specific OS). You can also save a security exception in the Mozilla browser.
And where are the home folders, I can not see them.
These folders are intended to be private (personal folders for each user). If you log in as a specific user, you should see only the home share for that user. I believe you need to access the NAS using SMB or CIFS with that user's credentials first (that triggers the creation of the folder).
As Admin, you can see them from the web ui. You can also access the full data volume with SMB using admin credentials (\\nas-ip-address\data in windows file explorer). You will see a home folder there, and if you navigate into it you can see all the user home folders.
Whats the point making a group when the only thing I can set is quota ?
If you have more than one user that have the same share access rights, then it is simpler to put those users into a group, and manage the permissions for the group as a whole (instead of for each user).
Isnt it possible to configure so some users cant see/access certain folders ?
Generally you can't prevent selecting users from seeing a share (other than the home folders). You can prevent them from accessing the contents (seeing what's in the folder).
Generally you can't prevent selecting users from seeing a share (other than the home folders). You can prevent them from accessing the contents (seeing what's in the folder).
