Support

Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? yes
Have I searched the tickets before posting? yes
Have I read the documentation before posting (which pages?)? yes
Joomla! version: 2.5.8
PHP version: (unknown)
MySQL version: (unknown)
Host: (optional, but it helps us help you)
Admin Tools version: 2.4.3

Description of my issue: I am recieving a 404 error when I attempt to "check connectivity" in a specific component. In the documentation of it, it says that minimum requirements:

"you must have enabled at least one of the following functions cURL , fsockopen , fopen , file_get_contents. In case your hosting provider doesn't allow loopback connections, then head to the second option."

I contacted my host, and they say that all of these functions are allowed.

Is the admin tool blocking any of these?  If so, can I run the PHP exec function? That is the "second option"

In an effort to find the problem with this 404, which I believe is caused by an SEF component, I am trying to eliminate the 404 page that is created by the template I am using. The template creator is suggesting that I rename the .htaccess file back to htaccess.txt.  This seems like a bad idea to me, but I can do it for testing purposes.  I can see that move creating all kinds of other problems on the site.

Any ideas on both of these would be a lot of help to me. Thank you.

Will do, thanks. I am just trying all options here. I cannot say that I think "Admin Tools caused the problem". Just trying everything I can think of.

My site is no Bluehost btw.

Trying your suggestions now...

Ok, I tried everything you reccomended and the end result is that it is not caused by admin tools.

Is the /logs folder supposed to have a 755 permission? As far as I know, the "owner" having write permissions is enough to create a file in there... Your component is able to write into that folder as I see your file in there.

The reason I ask, is the template maker has a custom 404 setup, and the SEF component is supposed to save a log file there when I have a 404. I am guessing that somehow the template 404 implimentation bypasses the trigger for the creation of that log file. In asking them how to shut down their custom 404, I was told to rename the .htaccess file all together. This just seems like a bad idea.. Maybe I will try it just for the heck of it.

Thank you for your ideas.

Nicholas, I have multiple problems running right now... I went ahead and tested your suggestions for my other problem (on accident) and that relates to my other problems.

I did the connectivity test, with the plugin disabled, and it worked.

Not working message:

Could not connect using "fopen,file_get_contents" but could connect with "cURL,fsockopen"

Working message:

Connection with "cURL,fsockopen,fopen,file_get_contents" successfully

I then did your reccomended test for the exception log. I got 3 exceptions, all of them say:

"Required header 'Accept' Missing"

Could you please make this ticket private and I will give you the information you need to log into my administrator side? The url is inside of the administrator in a component configuration.