ralieghnet
I understand what you are saying with respect to not modifying the main httpd.conf file. I simply did this to see if I could find the root cause of the problem. It is much faster then going through all the template files.
Far better and appropriate to troubleshoot by looking at the various log files. They will usually identify what is wrong by the nature of the errors.
Changing config file settings is usually just a "hit and miss' attempt to fix the problem when you don't really know what the reason is, because you have not properly analyzed the problem.
If anyone has any ideas how to original command would affect this it would be greatly appreciated.
The config command you referred to will not change file and directory permissions, so you need to look elsewhere.
Perhaps it happened after a ibay change, which reset permissions on the ibay that had been manually altered ?
Otherwise you may have manually changed something and forgot, or the other way around ie you forgot to reset permissions manually after other updates or changes, which you have now just done.