BugWP logo BugWP
Back to Community
Home / Community / Plugin → All-in-one security (aios) – security and firewall

Troubleshooting Common 6G Firewall Saving and Permission Issues in AIOS

16 threads Sep 9, 2025 Plugin → All-in-one security (aios) – security and firewall

Content

Why Can't I Save My 6G Firewall Settings?

Many users of the All-In-One Security (AIOS) plugin encounter a frustrating issue: they enable the 6G firewall rules, click save, but the settings fail to stick. The checkboxes for options like 'Block DEBUG method' or 'Block request strings' may appear empty after a page refresh, leaving your site without this layer of protection. Based on community reports, this is almost always a file permissions issue, not a bug with the plugin itself.

The Root Cause: File Write Permissions

Unlike the older 5G firewall rules that are written to your site's .htaccess file, the 6G firewall is a PHP-based firewall. When you enable it, the plugin needs to create and write a configuration file to this location on your server:

/wp-content/uploads/aios/firewall-rules/settings.php

If your web server (e.g., Apache, NGINX) does not have the correct write permissions for the uploads directory or the aios folder within it, this save operation will fail silently. You might see a PHP warning in your server's error log like:

PHP Warning: file_put_contents(.../wp-content/uploads/aios/firewall-rules/settings.php): Failed to open stream: Permission denied

How to Fix the 6G Firewall Saving Problem

Here are the most effective solutions, starting with the simplest and most common fix.

Solution 1: Manually Reset the AIOS Directory (Quick Fix)

This is often the fastest way to resolve the issue, as it forces the plugin to recreate its necessary directories with the correct permissions.

  1. Access your website's files using your hosting provider's file manager or an FTP/SFTP client.
  2. Navigate to the /wp-content/uploads/ directory.
  3. Locate and delete the entire aios folder.
  4. Go back to your WordPress dashboard and navigate to WP Security > Firewall > 6G Firewall Rules.
  5. Try enabling the 6G firewall protection and its sub-options again. The plugin should now successfully recreate the aios folder and the settings.php file.

Solution 2: Check and Correct File Permissions

If deleting the folder doesn't work, you may need to manually check and set the correct permissions.

  1. Using your file manager or FTP client, navigate to the /wp-content/uploads/ directory.
  2. Check the permissions (CHMOD) on the uploads folder. It should typically be set to 755.
  3. If the aios folder exists, check its permissions and those of the firewall-rules folder inside it. They should also be 755. The settings.php file, if it exists, should be 644.
  4. If the permissions are incorrect (e.g., 750 or 700</code}), change them to 755 for directories and 644 for files. You may need to consult your hosting provider for help with this, as they can confirm the correct user and group ownership for the files.

Solution 3: Enable Debug Logging

If the problem persists, enable debugging to get more detailed error information.

  1. In your WordPress dashboard, go to WP Security > Settings > Debug Logs.
  2. Enable both the Enable Debug Logging and Log Events to a File options.
  3. Reproduce the issue by trying to save the 6G firewall settings.
  4. Check the log file for any specific errors that might point to the exact nature of the permission conflict. The log location is displayed on the same settings page.

Important Note: A Change in How AIOS Works

It's helpful to understand that the All-In-One Security (AIOS) team has moved the 6G firewall rules from the .htaccess file to a PHP-based system. This change was made to ensure compatibility with a wider range of web servers, like NGINX, which do not use .htaccess files. This is why the saving process now relies on writing a PHP file to the uploads directory instead of modifying .htaccess.

Need More Help?

If none of these solutions work, the specific configuration of your hosting environment might be the cause. The most effective step is to contact your hosting provider's support team. Provide them with the error message from your logs and ask them to verify that the web server process (e.g., www-data, apache, nginx) has the necessary write permissions to the /wp-content/uploads/ directory.

Related Support Threads Support