Support

Please follow the instructions in https://www.akeebabackup.com/documentation/troubleshooter/athtaccessexceptions.html

Wait, no, you do NOT have to use the .htaccess Maker if you do not already use it. You just gave me no usable information so I made an guess on what could be the issue. My guess was wrong. So let's take this one step at a time.

Let's make sure that the problem is indeed caused by Admin Tools. In order to do so, try the following:

1. Try setting the Error Reporting level in your Global Configuration to "None". Many errors are caused by harmless PHP Notices and Warnings being output to the browser, breaking anything which requires HTTP header manipulation such as Joomla!'s session management, AJAX calls and download systems.

2. Try to replicate the issue after disabling the "System - Admin Tools" plugin. If you can still replicate the issue, it is not caused by Admin Tools. Disabling that plugin means that Admin Tools code (including the Web Application Firewall) is not running on your site.

If doing any of the above resulted in the issue still occurring, it's not related with Admin Tools and we can't help you. If doing any of the above did stop the issue from occurring, we'll have to do some troubleshooting.

First go to Admin Tools, Web Application Firewall, Configure WAF. Make sure "Log security exceptions" is set to Yes; if it's not, set it to Yes and click on Save. Now try reproducing your issue. Immediately after that, please go to Admin Tools, Web Application Firewall, Security Exceptions Log. The latest log entry at the top should have the date and time of when the issue occurred. Please copy the Reason and Target URL here so that we can further help you.

If, however, you do not see a log entry, or the Date and/or IP address do not match your last access, this problem is not caused by Admin Tools' WAF.

Can you please disable UploadShield in the Configure WAF page?

Hm, that's actually troubling. It means that Community Builder was trying to modify the Joomla! user record for a backend user from the front-end.

If you were trying to upload an avatar for a user with back-end access (e.g. a Super User or Administrator) then that's normal. After uploading the avatars for the back-end users I strongly recommend turning that option on again.

If this happened while uploading an avatar for another user there is reason to worry that something wrong is going on. However, knowing the people who developer Community Builder (they're just as security minded as us) I don't think this was the case at all.