[SOLVED] Still getting Apache 403 after adding Directory directive to Alias
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.
In the link that you have posted I do not see any example in which author has used home. I will try to duplicate the way you want it to be but can't promise how soon I can, as it will depend on my schedule.
I have seen people setting up alias for directories but not for the one which is under their home directory. Because user is the owner of his home. I doubt it will work without configuring acl.
Let me see if there is some alternate way to get this done.
Ok, I found a solution, and thank you because it was via the setfacl command you suggested. I had tried it previously but I was using the wrong user.
sudo setfacl -R -m g:www-data:rx /home/josh/Dev
What I don't understand is why I had to apply it so far up the path. Do you know why it worked at the Dev level but not static_test, or some other directory deeper in the path?
Great that you got it working. Please mark the thread as solved.
To answer your query I need to know the acl for /home/josh. You can find that using the following command:
Code:
getfacl /home/josh
The reason I am asking for this information because it appears to me that earlier you have setup acl for the only at /home/josh level but did not perform it recursively. Then you setup acl at /home/josh/Dev/bell_network_stuff/git/dev/static_test which didn't work because the user was not able to get into /home/josh/Dev itself then how it can reach so deep in the path.
I will be able to say for sure if I know how acl is set on /home/josh
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.