Apache treats it as an error but in this case, we can think of it as a warning/info given this was the wanted behavior. Yes, that error is the expected one and confirms the change to make user.ini private is working. AH01630: client denied by serverĬonfiguration: /opt/bitnami/wordpress/.user.iniÄ«ut I take it that is expected, right? Our intention was to indeed block the user.ini By the way, I do receive this warning now on the BNSupport diagnostic: So you should check for configuration related to filtration based on hostname, IP address, and other characteristics of client. Apparently this is actually desired behavior, though Apache throws an error. In thta case you must add this image manually or remowe this record from database and add again in BO. The default Apache config includes Deny from all in the block the DocumentRoot - this must be changed to allow access If you change.Let me know if this helps!Īuto_prepend_file = â/home/path-to-file/wordfence-waf.phpâ If ther isnt folder 3 that means there is no base image so you cant regenerate thumbnails for this image. ![]() Php_value auto_prepend_file '/path/to/waf/wordfence-waf.php' ![]() Since your Server API is actually Litespeed, you will want to add this code to your htaccess file, but make sure to adjust the file path to point at your wordfence-waf.php: 'client denied by server configuration' means that the Linux server itself forbids the access to the file, not Apache. ![]() user.ini file using FTP or a file manager, what sort of code exists inside of it? If any? What is strange is your setup shouldnât even be using a. This was the thread I wanted input on, could this fix my issue?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |