pcfq_openfile: unable to check htaccess file

[MarkEHansen]

I have CentOS 7.0 and am trying to install the Roundcube Webmail application, version 1.1.2 (complete version).

I've installed Apache web server, MySql (actually, Mariadb) and PHP, all at or above the required versions.
I've followed the instructions for getting the application up and running, but when I try to access the main page of the application (index.php) I'm getting the following error in the httpd server error log file:

Code: Select all

[Sun Sep 13 09:06:34.096832 2015] [core:crit] [pid 29683] (13)Permission denied: [client 10.1.1.70:55708] AH00529: /var/www/html/roundcube/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable and that '/var/www/html/roundcube/' is executable

I understand that the directories leading up to and including the roundcube directory must have search permission (x) and that the .htaccess file in the roundcube directory must have read permission for the httpd user (apache). Both are true - I've checked multiple times.

I'm guessing there is something else that I'm missing. Note that I've placed a file named info.php in the /var/www/html directory to provide PHP info and that works when I browse to it.

I've gone through the installation instructions and verified I've done everything multiple times.

What am I missing? Is this an SE Linux issue? The /var/www/html is the default location for web content for Apache, so I thought SELinux didn't come into play.

Do I need to change some configuration in the httpd config to allow it to use the .htaccess files? I haven't touched the httpd configuration other than what was specified by the Roundcube installation instructions.

I've reported this on the Roundcube community forum, but after a week I've still received no response. I'm hoping this is a more general Apache problem.

Thanks for any help.

[gerald_clark]

Try "restorecon -R /var/www" .

[MarkEHansen]

Thank you Gerald. The restorecon command got me past this issue!

... now on to the next problem

[Shore-Bank]

This also fixed my issue (CentOS 8, apache 2.4.37).

I have no idea why it would've needed that in the first place, but in fairness, I had done a system update not long before. We're back up and running on that, which is good.