Support

Components, Admin Tools for Joomla, Web Application Firewall, WAF Exceptions.

Click on New on the toolbar.

Component: select the component name which corresponds to com_nobossajax

Click on Save & Close.

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. Note that to do that you first have to go to Components, Admin Tools, Web Application Firewall, Configure WAF and set "Defend against plugin deactivation" to No. 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.

3. If you suspect an issue with the .htaccess file, replace its contents with the contents of the stock htaccess.txt file shipped with every version of Joomla!.

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. In this case, you will have to do some .htaccess troubleshooting. You may need to read the general .htaccess troubleshooting page, as well as the page on finding out necessary .htaccess exceptions.

Ah, it's a Google API with scopes! Had you told me that I would have told you already what to do.

The problem is Google using full URLs as API scopes, e.g. https://www.googleapis.com/auth/calendar.readonly.

Go to the .htaccess Maker.

Set "Protect against common file injection attacks" to No.

Click on Save & Create .htaccess in the toolbar.

I believe you will find that it's working now.

At least that's the problem I had with Google integration (Login with Google) on my sites, and how I fixed it :)