Question

AH01797: client denied by server configuration

Hi,

Today morning i was trying to access A wordpress and a Moodle app in the dropplet, but i am receiving the 403 Forbidden error when accesing admin panel in WP and in Moodle in general. I have checked the hosts configuration files and updated with the appropiate rules, also i checked permissions on folders and files an nothing resolves the issue.

I am detecting some wierd behavior on .htaccess files, whenever i want to change the rules in the htaccess file in wordpress installation the changes are reverted, despite i disbled all plugins manually and deleted the file, it appears again and maybe one of the rules in this file is causing the forbidden error.

I was trying to do anything possible, but now i am stuck and cannot try anything else, but restore the dropplet from a backup.

Any hint would be great,


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Hello, @JuanSaudade

You can examine the Apache/Nginx error log in order to track down the source of the issue here.

Also, you can double-check the file/folder ownership and permissions and make sure that they’re correct.

The log can be accessed using the cat, tail or the less command

  1. sudo tail -n 2 /var/log/apache2/error.log

Substitute the number of lines that you would like to examine in place of the number 2 in the command.

If you’re using Nginx you can use the following command:

  1. tail -n 2 /var/log/nginx/error.log

Regards, Alex