Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
chroot_list_enable
If activated, you may provide a list of local users who are placed in a chroot() jail in their home directory upon login. The meaning is slightly different if chroot_local_user is set to YES. In this case, the list becomes a list of users which are NOT to be placed in a chroot() jail. By default, the file containing this list is /etc/vsftpd.chroot_list, but you may override this with the chroot_list_file setting.
Huh! ssh has nothing to do with vsftpd.
I guess you're trying to setup sftp (that is based on ssh), but is totally different from ftp (based on a ftp server like vsftpd)
So using the vsftpd config posted above and using ftp, your user can transfer files in the desired location using the ftp protocol
If you want to use sftp, have a look here for an example (written for debian, but applies to any distro)
Yes ok this works but the problem is that i can't use a path without users name like:
Code:
/home/nginx/domains/mydomain.com/public
I must have the users name on the link to work....
Code:
/home/username
And the second problem is permissions as i have nginx:nginx and all working great with my site and if i change them to root:root then the site is not working..
Yes ok this works but the problem is that i can't use a path without users name like:
/home/nginx/domains/mydomain.com/public
I must have the users name on the link to work....
/home/username
Are you talking about sftp or ftp? In both cases if you set the user homedir the same as the docroot, there should be no problem.
Quote:
And the second problem is permissions as i have nginx:nginx and all working great with my site and if i change them to root:root then the site is not working..
As I've told you nginx does not bother about ownership of docroot, assuming that you have 755 for folders and 644 for files
I am talking about sftp and yes i have 755 for folders and 644 for files but if i set the nginx folder to root:root then is not working the site
Please define "is not working the site". What is the error you get?
BTW why set ownership to root:root and not let the directory owned by the normal user?
Please define "is not working the site". What is the error you get?
BTW why set ownership to root:root and not let the directory owned by the normal user?
I am getting a blank white page and on error logs i get permission denied.
I am getting a blank white page and on error logs i get permission denied.
It works only with nginx:nginx permissions....
Thanks
You didn't mention your distro, so I think you're using a RHEL or derivative and the error you get is because of SELinux.
If that's the case disable it temporarily and see what you get.
Or use:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.