Same problem for me !
Error 500 when Falcon Engine enabled and all is right returning to old htaccess file !
Please help.
Regards,
Olivier
Same problem for me – further info
Thank you for your work on Wordfence, including Falcon.
The site was on WordPress 3.8.x with WordPress 5.0.2; Falcon was working fine.
Upgraded WordPress to 3.9, and Wordfence from 5.0.2 to 5.0.3; the site worked fine (the upgrade disabled Falcon).
When I enabled Falcon, I got “Internal Server Error”; restoring .htaccess brought the site back OK.
The error log shows: /var/www/html/wordpress/.htaccess: order not allowed here
Re-enabling Falcon and commenting out line 2 of .htaccess: “Order Deny,Allow”, the site seems OK,
although it may not be secure or working totally correctly without that line.
Now running on Basic Caching until this is fully resolved.
Hi,
This is because your site admin has disallowed you to use IP blocking in .htaccess. It’s something specific to your config, not a bug in Wordfence. Read this for more:
http://stackoverflow.com/questions/14250674/htaccessorder-not-allowed-here
Also google around for the specific error you’re getting, it’s a common problem.
I got your email re the beta, and we’re not going to add a fix for this because it’s an issue with your config and not Falcon.
Regards,
Mark.
I checked my virtual host configuration and it seems already have correct configuration.
<Directory /var/www/virtual/mywebsite.com/htdocs>
Options -Indexes Includes FollowSymLinks MultiViews
AllowOverride All
Order allow,deny
Allow from all
</Directory>
@mmaunder,
After I read your answer, I thought this problem is related to user on my web server.
I changed my website’s owner permissions from “user:www-data” to “www-data:www-data”
And now, It worked for me.
cd /var/www/mywebsite.com/
find -exec chown -R www-data:www-data {} \; -print
find -type d -exec chmod 755 {} \; -print
find -type f -exec chmod 644 {} \; -print
chmod 600 wp-config.php
chmod 604 .htaccess
Hi Mark,
Pecking around trying to find out what exactly “Falcon” is?
This one makes me a little nervous since it writes to htaccess –
Can we enable / disable it? What does it do? Or where can I read about it?
Thanks!
