Apache Error 13permission Denied Access To / Denied
Contents |
files will yield something like: (13)Permission denied: access to / There are a few things that could be the problem: Make sure it's not denied by Apache apache error log permission denied Most apache Configurations have something like this in there:
Error 13 Permission Denied Filezilla
The solution in that case is to add another Directory entry in your httpd.conf to allow access to that directory. Make sure Apache has Read, Execute Permissions The next thing to check is that Apache has read and execute permission (rx) on directories and read permission on files. You can run chmod 750 /dir (to give -rwxr-x--- permission) or chmod 755 /dir (to give -rwxr-xr-x error 13 permission denied sickbeard permission), etc. Make sure that the Directory Above has Execute Permission This is the one that tends to get me. Suppose you are creating an Alias like this: Alias /foo /tmp/bar/foo Now you have made sure that apache can read and execute /tmp/bar/foo by running chmod 755 /tmp/bar/foo, but you also need to give Apache execute permission to /tmp/bar/ otherwise it cannot traverse the sub directory foo. If Running Security Enhanced Linux (SELinux) Another possibility for this error is that you are running SELinux (Security Enhanced Linux), inwhich case you need to use chcon to apply the proper security context to the directory. One easy way to do this is to copy from a directory that does work for example /var/www/ chcon -R --reference=/var/www /path/to/webroot Tweet Permalink | Add Comment | add to del.icio.us | Tags: apache, alias, permission, httpd Related Entries Apache Security Patches on CentOS / RHEL - November 22, 2013 20 ways to Secure your Apache Configuration - December 6, 2005 CheatSheet for Apache - October 7, 2005 14 people found this page useful, what do you think? UsefulVery UsefulNot Useful Comments Another issue could be that your u
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers error 13 permission denied python or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x
Error 13 Permission Denied Linux
Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only
Mount Error 13 Permission Denied Ubuntu
takes a minute: Sign up Apache 13 permission denied in user's home directory [closed] up vote 36 down vote favorite 9 My friend's website was working fine until he moved the document root from /var/www/xxx to /home/user/xxx. Apache gives 13 https://www.petefreitag.com/item/793.cfm permission denied error messages when we try to access the site via a web browser. The site is configured as a virtual directory. All the Apache configurations were unchanged (except for the directory change). We tried to chmod 777 /home/user/xxx, chown apache /home/user/xxx. But they didn't work. Is there some kind of security feature set on the user's home directories? The server OS is CentOS (Godaddy VPS). Any help is appreciated! Thanks! apache permissions share|improve this question edited Oct 15 http://stackoverflow.com/questions/1225594/apache-13-permission-denied-in-users-home-directory '12 at 6:32 Santosh Kumar 5,48373175 asked Aug 4 '09 at 3:18 Dave 4,47442638 closed as off topic by Will Jan 25 '11 at 13:51 Questions on Stack Overflow are expected to relate to programming within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question. 3 Should go on serverfault. –g . Aug 4 '09 at 3:21 Didn't know about that until you mentioned it =) I guess I'll give it a go. Why they keep two (maybe more?) sites anyway? Isn't it better to centralize those categories? –Dave Aug 4 '09 at 3:50 @Dave: stackoverflow.com is for programming questions; serverfault.com is for sysadmin/server questions; superuser.com is for general "power users" and other misc computer related questions. Helps people focus on their areas of expertise I suppose. –Josh Aug 4 '09 at 13:47 Can the question (and it's answers) be migrated over to serverfault - it is a good question, and cleared up an issue for me. I have also learned a little more that I would add as an answer for it if it was not closed. –Danny Staple May 11 '11 at 10:05 I left a
the rsync command to migrate files from an old webserver to a new one. What I didn't notice right away was that the rsync changed https://techblog.jeppson.org/2015/02/fix-apache-permission-denied-errors/ the permissions of the folder I was copying into. The problem presented itself http://blogs.n1zyy.com/n1zyy/2011/12/08/stumped-by-13permission-denied-file-permissions-deny-server-access/ with a very lovely 403 forbidden error message when trying to access any website that server hosted. Checking the logs (/var/log/apache2/error.log on my Debian system) revealed this curious message: [error] [client 192.168.22.22] (13)Permission denied: access to / denied This made it look like apache was denying access for some permission denied reason. I verified apache config and confirmed it shouldn't be denying anything. After some head scratching I came across this site which explained that Apache throws that error when it encounters filesystem access denied error messages. I was confused because /var/www, where the websites live, had the appropriate permissions. After some digging I found that the culprit in my case was not error 13 permission /var/www, but rather the /var directory underneath /var/www. For some reason the rsync changed /var to not have any execute permissions (necessary for folder access.) A simple chmod o+rx /var/ resolved my problem. Next time you get 403 it could be underlying filesystem issues and not apache at all. apacheDebianlinuxpermissionsrsync Post navigation Previous PostRemove and re-install a Debian packageNext PostConvert xenserver 6.5 to software RAID 1 Leave a Reply Cancel reply Your email address will not be published. Required fields are marked *Comment Name * Email * Website WelcomeThis blog is meant as a dumping ground for my technical musings. It is mostly for my own sake but I am making it public in the off chance that it might be useful to someone else. If you find the content on this site useful, please donate to contribute to server costs. Thank you! TagsActive Directory Android apache BASH BSD CentOS chromebook Chromebook Pixel Chrome OS crouton Debian DNS find freeBSD freeNAS grep guacamole hardware linux Linux Mint LVM mysql openvpn owncloud PCI passthrough php Plex RAID regex rsync scripting sed Sophos UTM Splunk
8, 2011 by n1zyy I was just pretty stumped by the following Apache error, in /var/log/httpd/error_log: [Thu Dec 08 21:53:28 2011] [error] [client 192.168.1.2] (13)Permission denied: file permissions deny server access: /var/www/html/aml/i ndex.html The error implies it's a filesystem permissions issue, and the Apache site explains that it's almost always related to filesystem permissions, not Apache configuration. But this was exasperating, because the file ownership was apache.apache, and index.html was chmod 755. Apache could absolutely access it. But then the Apache docs made a passing mention that sometimes it was related to SELinux errors. Sure enough, that's exactly my problem: [matt@bos aml]$ ls -alZ drwxr-xr-x. apache apache unconfined_u:object_r:httpd_sys_content_t:s0 . drwxr-xr-x. root root system_u:object_r:httpd_sys_content_t:s0 .. -rw-r--r--. apache apache unconfined_u:object_r:httpd_sys_content_t:s0 .htaccess drwxr-xr-x. apache apache unconfined_u:object_r:user_home_t:s0 images -rw-r--r--. apache apache unconfined_u:object_r:user_home_t:s0 index.html drwxr-xr-x. apache apache unconfined_u:object_r:user_home_t:s0 stylesheets Note that the directory, and the .htaccess file I touched, have the httpd_sys_content label, which is appropriate here. But the other files show user_home_t. This apparently precludes Apache from being able to see them. Where this went wrong is that, to get them onto the server, I scp'ed them from my desktop to my home directory on the webserver, and then cp'ed them to /var/www/html. In doing so, they picked up the user_home_t label since they were in my home directory. A quick sudo restorecon -r . got everything sorted out. There may be a more elegant way, but this worked for me. This entry was posted in Uncategorized by n1zyy. Bookmark the permalink. 30 thoughts on “Stumped by (13)Permission denied: file permissions deny server access ?” i5junkies on January 30, 2012 at 4:37 pm said: Thanks for this posting. It helped me fix the problem and running. GREAT post!!! Reply ↓ Philip on February 7, 2012 at 5:42 am said: Thank you for this. Reply ↓ Georgi on March 6, 2012 at 10:58 am said: Thank you VERY much for posting that out! Exact same problem here, mother of god, do I hate selinux… Reply ↓ Chris on March 9, 2012 at 4:47 am said: This post was exactly the solution to the error I was getting, thanks. Reply ↓ bob on May 7, 2012 at 2:58 pm said: THANKS! I had no idea this was a thing. Saved my day. Reply ↓ Bobby W on May 31, 2012 at 3:48 pm said: Had the same problem, yours didnt work exactly. I did sudo restor