Blocks Staging Site

Hi @trutherone

Is there any error log logged in php error log file?

I will create internal ticket for this to check The .htacces rules of the parent folder are generally applied to the child and WP staging plugin makes the stagin site as child folder up to I know. let me know if that is not the case.

So hope fully the firewall aios-bootstrap.php getting included as auto_prepend is not the the issue.

Remove whole .htaccess try remove certain section of it and may corss check what exact making issue.

#BEGIN All In One WP Security"
 #END All In One WP Security"

It might be due to firewall .htaccess code as the aiosboot-strap.php of parent and child called two times hope that is not making issue.

# Begin AIOWPSEC Firewall
	<IfModule mod_php5.c>
		php_value auto_prepend_file '/var/www/html/aios-bootstrap.php'
	</IfModule>
	<IfModule mod_php7.c>
		php_value auto_prepend_file '/var/www/html/aios-bootstrap.php'
	</IfModule>
	<IfModule mod_php.c>
		php_value auto_prepend_file '/var/www/html/aios-bootstrap.php'
	</IfModule>
# End AIOWPSEC Firewall

Regards

Hi,

Are you referring to the staging site when you write ‘child’ i have a child-theme and that is all setup ok and is not the issue this problem occurred after setting up the staging site directly on my server hosting account; they have a single click option to allow creating a staging site so you don’t need to use a 3rd party plugin. Noted: there is a .htaccess file in both the parent(production) site files AND one in the staging sites files since the sites are carbon copies of one another. I noticed that the files are identical and there might be some conflict going on. Also the two lines which are injected to the top of wp-config.php, as you suggest, may be clashing since they appear in both sites; production and staging. Rather than messing with .htaccess, which i don’t like to do, would it be better to just turn Firewall option off in the plugin? I can do without it anyway as i have Firewall settings at the server hosting level.

UPDATE:

In the staging site i just commented out those ‘Firewall’ lines at the end of .htaccess and the two lines they write to wp-config.php and the 500 error has gone. So you were spot on the issue. Ill leave the Firewall tab and wait for an update on the plugin which we like for the 2FA and other features

Thanks for your attention in diagnosing this issue.

Hi @trutherone

Glad to know the 500 errors are solved.

If you deactivate and then activate (Reapply the settings from notice) again the AIOS plugin from the Plugins list the firewall-related lines should be corrected as per the created staged site folder path.

Regards