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 I 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 and go to the last page. The last log entry should have the date and time of when the issue occurred. Please copy the Reason and Target URL here so that I can 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.

Something in your account of the events I don't understand. You said that you renamed the file back to main.php, re-enabled Admin Tools' plugin and the site works fine. If the site works fine now, how is there a problem which you are sure that is created by Admin Tools? Didn't you just say that after enabling Admin Tools there was no problem?

This is not an Admin Tools issue.

Please look up HTTP error 503 and HTTP error 504. These are networking errors which have to do either with your host or your other admin's ISP. Since you can access your site it's most likely the other party's ISP.

I mean, all the while you claim it's an Admin Tools issue but you can't even reproduce the issue yourself. And you insist that it's an Admin Tools issue? Which happens even when the plugin is disabled, i.e. when NO Admin Tools code is running? And only happening to the other admin? Think about it and draw your conclusions.

First you said:

ok, on point 2 I disabled admin tools, renamed the php file back to main.php and loaded the site. All works as it should. I then re-enabled admin tools, and it still works.

Translation: enabling or disabling Admin Tools makes no difference to the issue. As a result, it is not ad Admin Tools issue (if it were, enabling Admin Tools should cause the problem to occur).

Then you said:

I do not have a problem at my computer, but the other super admin at another ip address is having a problem.

Translation: it only happens to a specific user, not everyone. As a result, it is not an Admin Tool sissue (it would happen for all users)

Let me reiterate that 503 and 504 errors are networking errors. As such they can't be affected by Admin Tools because Admin Tools has no say on your host's server network configuration for the simple reason that it does not have root privileges or knowledge of your host network's topology.

And now you are saying:

if it is not an admin tools issue, why, when the file /system/admintools/admintools/main.php is changed to main-disable.php, the problem goes away?

which is THE OPPOSITE of what you already said.

Please make up your mind. Disabling the plugin can either have no effect (your first reply) or do have an effect (your last reply). Remember that at this point I am not sitting in front of your computer, I am not your host, I am not your ISP, I am not a psychic and I rely on the information you relay to help you. If what happens is white and you tell me that black is going on then, yeah, expect sarcasm (which in previous post it wasn't; I was actually asking you to read the pages and draw your conclusions based on that information and what you were describing that's going on) and expect me to close the ticket. Like I am doing now. Sorry, I am only here to help people who want to give me accurate information when I ask for it, i.e. they want to get helped.