Errors immediately on installation

If after or during activation you have a failure that results in an error, either 500 error or ‘your site is having technical difficulties’, there is a manual step you need to carry out to get your site working again.

Apache & Litespeed Servers

Fullworks security adds a new section to the .htaccess file to run the WAF code before WordPress is installed. This is for performance reasons, to stop the whole of WordPress being loaded each time a request is made.

If your installation has failed and you are unable to access your site use your control panel file manager, sftp or any other method to directly edit your .htaccess file in you web root folder.

Delete the content between the two markers ‘# BEGIN fullworks-security’ and ‘# END fullworks-security’ ( you can delete the markers if you wish ).

This is what you are looking for

# BEGIN fullworks-security
php_value auto_prepend_file "/var/www/html/wp-content/plugins/fullworks-security-premium/fullworks-security-waf.php"
<Files ".user.ini">
<IfModule mod_authz_core.c>
        Require all denied
</IfModule>
<IfModule !mod_authz_core.c>
        Order deny,allow
        Deny from all
</IfModule>
</Files>

#  END fullworks-security


and this is what it should look like after editing

# BEGIN fullworks-security

#  END fullworks-security


Nginx Server

Fullworks security creates or adds a new section to the .user.ini file to run the WAF code before WordPress is installed. This is for performance reasons, to stop the whole of WordPress being loaded each time a request is made.

If your installation has failed and you are unable to access your site use your control panel file manager, sftp or any other method to directly edit your .htaccess file in you web root folder.

Delete the content between the two markers ‘; BEGIN fullworks-security’ and ‘; END fullworks-security’ ( you can delete the markers if you wish ). If the file only contains the Fullworks code and nothing else, you can delete the whole file.

This is what you are looking for

; BEGIN fullworks-security
auto_prepend_file = '/var/www/html/wp-content/plugins/fullworks-security-premium/fullworks-security-waf.php'
;  END fullworks-security


and this is what it should look like after editing

; BEGIN fullworks-security
;  END fullworks-security

Raise a support ticket

We try hard to ensure Fullworks Security installs cleanly first time, however there are many combinations of webservers and so please raise a ticket if you had an installation issue so we can resolve the issue for you.

Was this helpful?