pcfg_openfile: unable to check htaccess file, ensure it is readable
I'm getting the following error after moving a site to a new environment. The site was restored via a backup. We are able to access the site but not make any changes.
Permission denied: [client 5.188.210.101:12971] AH00529: /home/lexofc390/public_html/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable and that '/home/lexofc390/public_html/' is executable
[root@lexington ~]# stat /home/lexofc390/public_html
File: "/home/lexofc390/public_html"
Size: 4096 Blocks: 8 IO Block: 4096 directory
Device: 801h/2049d Inode: 234997889 Links: 14
Access: (0755/drwxr-xr-x) Uid: ( 1002/lexofc390) Gid: ( 99/ nobody)
Access: 2020-04-27 20:05:06.677315844 +0000
Modify: 2020-04-24 22:56:04.133792348 +0000
Change: 2020-04-28 00:26:53.347480748 +0000
Birth: -
Enable File Protect is enabled in Tweak Settings -> Security.
-
If you change the public_html permissions to 750 does the issue persist? Fileprotect should be doing that automatically as noted in the documentation: The EasyApache 4 FileProtect Option | cPanel & WHM Documentation What are the permissions of the .htaccess file? 0 -
the issue was still occuring when they were 750. We appear to have resolved the issue though. We were also getting a "Reading exif data not supported with this php installation" error in a different log file. So we enabled the php-exif extension and everything seems to be working normally now. I dont know enough to know if these could somehow be related, but we are no longer seeing this error? 0 -
I wouldn't necessarily think they would be related but I am glad to see that the error is no longer occurring. What are the current permissions/ownership of the public_html for the account? 0 -
750 and lexof390 is the owner and the group is nobody 0 -
With fileprotect enabled that is what it *should* be if it's not set to that with the setting enabled It won't work. 0 -
yes thats enabled. I think we are all good now. I appreciate your quick responses!! Thanks 0
Please sign in to leave a comment.
Comments
6 comments