Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
running lighttp webserver
config
port 80
user www-data
group www-data
www-data dir /home/west/Movies
also tried /var/www/html
ownership www-data www-data
rw-r--r--
from local browser 127.0.0.7
returns 403
index lighttp.html exists
# sudo lighttp-enable-mod dir-listing
done
#sudo service lighttpd stop
#sudo service lighttpd restart
#sudo service lighttpd force-reload
#sudo service lighttpd status
all report no errors
but still browser returns 403
sudo netstat -t -l -p
shows lighttpd serving on port 80
An “index” file must be named index.htm(l), absent changes in configuration.
It’s also not clear what the permissions of your DirectoryRoot are. A 403 error indicates a permission or authority issue.
An “index” file must be named index.htm(l), absent changes in configuration.
It’s also not clear what the permissions of your DirectoryRoot are. A 403 error indicates a permission or authority issue.
# sudo lighttp-enable-mod dir-listing
so no index is needed
permissions have been set :
user:user did not work
www-data:www-data did not work
restarted service, reloaded, rebooted over days, did not work
Um. Show us the permissions you've set on the parent directory and the file/page you're wanting to load.
Hard to believe there's no indications in the logs...
# sudo lighttp-enable-mod dir-listing
so no index is needed
permissions have been set :
user:user did not work
www-data:www-data did not work
restarted service, reloaded, rebooted over days, did not work
error log shows no errors
What about access.log? Does it log the 403 respones?
I'm not familiar with lighttpd logging, but according to this, you can enable debugging to see if you get something useful.
Quote:
Originally Posted by scasey
Um. Show us the permissions you've set on the parent directory and the file/page you're wanting to load.
Hard to believe there's no indications in the logs...
Also to add to what scasey posted above, make sure that the docroot directory has 755 permissions and the files just 644.
If all permissions appear correct, perhaps your system uses SELinux, and the web files have the wrong label. You should then have messages in /var/log/audit/audit.log (at least if it is RHEL or a derivative).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.