Pete Houston wrote:
> No, I was meaning the SELinux context. If SELinux is preventing access
> the details will be in the audit log. If you have just created this tree
> within your home directory, it probably won't have the context Apache
> expects and you might either need to change the contexts
On Sat, Feb 16, 2013 at 12:37:12PM +0100, Gergely Buday wrote:
> Pete Houston wrote:
> > If it still fails after that, check the audit log to make sure the
> > directory has the right context.
>
> Oops, could you explain what a context is? This one:
>
> http://httpd.apache.org/docs/2.2/mod/direct
Pete Houston wrote:
> Also, check your various Allow and Deny settings to make sure access to
> that directory is permissible.
Would it be possible to make Apache write which rule made it to refuse
access? I have set the LogLevel to debug, but that did not help.
I checked the Deny rules and none
On Sat, Feb 16, 2013 at 12:00:15PM +0100, Gergely Buday wrote:
>
> I created a 'web' group and put my user and apache into it, and gave
> 640 for the files and 750 for the dirs.
>
...
>
> $ ls -ld wp-admin/
> drwxr-x--- 9 gergoe web 4096 Sep 7 08:54 wp-admin/
>
> What do you suggest to fix thi
Hi there,
I would like to access a wordpress installation in my home directory
on my Fedora box through Apache.
When I try to access its wp-admin dir, I get
You don't have permission to access /kolozsvar/wp-admin on this server.
I have an AliasMatch directive in /etc/httpd/conf/httpd.conf:
