How to solve “.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable”

advertisement

My error log shows:- 

[Sun Jul 13 01:15:32 2008] [crit] [client 218.208.xxx.xxx] (13)Permission denied: /home/mydomain/public_html/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable

And the site is showing “403 Forbidden Error”.
At first, I suspect it’s .htaccess problem, but actually it’s caused by Frontpage Extension.

To solve “.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable” follow the steps below:-

  • Login into your CPanel account
  • Click on “Frontpage Extensions” icon
  • Click on “Reinstall extensions” button beside your problem domain.
    *If you do not use any frontpage extensions, it’s good to uninstall this extension
  • Done. The “.htaccess pcfg_openfile: unable to check htaccess file” problem has been fixed.

** If you are not on CPanel hosting, please contact your system administrator to fix the problem. ***

Credit: The HungryCoder



Tags: , , , , , ,

«
»

Related Post


If you think this article helps you to solve your problem and clear your headache,
feel free to buy me a drink :)

11 Responses to “How to solve “.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable””

  1. Jo says:
    June 7, 2010 at 2:11 pm

    You are my hero! Thank you

  2. Mara Mora says:
    June 2, 2010 at 9:48 pm

    Thanks for this post. You saved me. transferring my flders and Frontpage extension from VPS to VMWare.

    Thanks for your post.

    Best regards

  3. AsoeLaoet says:
    April 2, 2010 at 1:53 am

    Thanks … very good posting ..
    Permission denied: xxx/public_html/.htaccess pcfg_openfile: GONE!
    keep posting bro!

  4. robotech says:
    March 5, 2010 at 11:02 am

    ——-UM oops another update – ————————–

    OOps I lost access to the folder with 665 so um – lest stick with 775?

    Heheheh

  5. robotech says:
    March 5, 2010 at 10:58 am

    Update!!!!!——————————————-

    —————-665 permissions works and is safer!!!————————-

    At least using a software called coffee cup HTML you can put the permissions to 665 – that way the world can not write to it – I guess the moral here was to give the DIR execute permissions———————-

    Sure hope this helps some one – and protects them – Sory for the fake email addy too! ;)

  6. robotech says:
    March 5, 2010 at 10:52 am

    Looks like I had to make the folder 777 – I dont like that but it is working – so Ill play with it and let ya all know if you can back 777 down at all like to say 775 ?

  7. zanlok says:
    February 13, 2010 at 6:43 pm

    THANK YOU!

    This just saved me a boatload of time. Can’t say how I messed my server up so madly, but me converting everything over to use svn (as root) made a the sites totally die even when I chowned things to the users. This cleared it up and I would *never* have guessed what the problem was!

  8. Franco says:
    February 13, 2009 at 2:00 am

    cool….ill buy u tons of drinks :D

  9. Rui Cruz says:
    January 3, 2009 at 3:44 am

    Thank you,

    This solve my issue!

    Rui

  10. john says:
    September 14, 2008 at 12:35 pm

    THANKS!! great post. This helped me solve my problem very quickly

  11. j0k3r says:
    July 27, 2008 at 7:35 pm

    Also you’d check owner and chmod of files/dirs ;)

Leave a Reply