Support

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.

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 you are on GoDaddy please wait for 1-30 minutes for the changes to be effective. Then, retry loading the problem page. If you can still reproduce the error, then it is not caused by .htaccess Maker.

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.

Hm, wait, based on what you said I guess that you are using GeoIP blocking, i.e. blocking requests from specific countries.

I know for a fact that AcyMailing's CRON job URL works on hundreds other clients and that it doesn't have anything else in it which would be caught by Admin Tools.

What you never told me is how you trigger the CRON URL, but you do mention wget. I make an educated guess that you are using a third party service OR a third party server which uses wget to access the CRON URL. Wget is completely irrelevant. What is relevant is the IP of whatever is trying to access the AcyMailing CRON URL. If that IP belongs to a country or continent that you have blocked it's perfectly reasonable that Admin Tools blocks it: this is what you asked it to do. In this case you would not see anything in the Admin Tools security exceptions log since GeoIP blocking is, by default, not reported (that's something you can configure in the Configure WAF page).

I would recommend enabling Admin Tools but turning off GeoIP blocking. Alternatively, find out which IPs are used to trigger the CRON URL and add them to the "Never block these IPs" list in the Configure WAF page.