Support

This is a known interaction between Linguise and one of Admin Tools’ Web Application Firewall (WAF) features. Linguise fetches your pages through your site using requests which can look like parameter tampering to the WAF, so allowing its IP addresses is often not enough.

Please try the following:

1. In your site’s backend go to Components, Admin Tools, Web Application Firewall, Configure WAF.
2. Click on the Request Filtering tab.
3. Set Block Suspicious Core Parameters to No.
4. Click on Save & Close.
5. Try a translated page again.

If this solves the problem, you are done.

If you still get the 403 error, please check the following, as it tells us where the block comes from:

1. Go to Components, Admin Tools, Web Application Firewall, Blocked Requests Log (in older versions of Admin Tools: Security Exceptions Log) and look for entries dated at the time you loaded the translated page. If there is one, please send us its reason (e.g. “Blocked Suspicious Core Parameters”, “IP blocked”, and so on) and the URL it lists.
2. If there is no entry at that time, the block is most likely not coming from Admin Tools’ WAF, since Admin Tools always logs the requests it blocks. In that case we believe the 403 is produced by something before Joomla is even loaded: your .htaccess file or your host’s server configuration (for example a mod_security ruleset). We can’t be certain of this without testing, so to rule Admin Tools out, please do the following, one step at a time, testing the translated page after each step:
   1. Using FTP or your host’s file manager, rename plugins/system/admintools/services/provider.php to provider-disable.php. This temporarily turns Admin Tools off. If the translation works now, tell us and stop here.
   2. If it still fails, rename it back to provider.php. Then rename .htaccess to .htaccess-admintools-bak and rename htaccess.txt to .htaccess. If the translation works now, tell us and stop here.
   3. If it still fails, the 403 comes from your server or hosting environment. Please ask your host (all-inkl) to check their server / mod_security logs for the blocked URL around the time of your test.

Whatever the outcome, please make sure you have renamed provider.php back to its original name and, if you restored it, that you put your original .htaccess back (rename .htaccess-admintools-bak to .htaccess) once you have finished testing. Your site is not protected by Admin Tools while provider.php is renamed.