Connection broken from Konqueror to Apache only certain DIRs

[OdinsDream]

I'm attempting to set up ampache, from ampache.org. The installation seems pretty simple. Most of the configuration is done through a web-interface.

The directory structure I have is:
/home/httpd/htdocs/
/home/httpd/htdocs/ampache
/home/httpd/htdocs/ampache/docs
/home/httpd/htdocs/ampache/docs/images
/home/httpd/htdocs/ampache/docs/admin

The setup file is: ampache/docs/setup.php

First of all, my apache configuration is working. I'm able to view other PHP files, as well as get PHP information and show it on a test page.

When I go to:

http://localhost/ampache/docs/setup.php

I get "Connection to host localhost is broken"

I also get this if I try to just list the contents of docs

However, I can list the contents of ampache, and even ampache/docs/images.

I cannot list the contents of ampache/docs/admin

For the life of me, I cannot figure out what the difference is between these directories, and why I can access one and not the other. Any help is appreciated.

[OdinsDream]

Does anyone have suggestions? Is this a permissions problem? I've chown'ed all the files under ampache to root, recursively...

[OdinsDream]

Well, I tried the webpage from a windows computer, and instead of getting the message box error, I got a page full of PHP errors, which was much more helpful.

I've been able to trace the problem to the code in index.php. Sorry for the trouble.

Although, it's still peculiar that Konqueror did not show me the PHP errors in the webpage itself, but just gave me a generic message. Very unhelpful.

[mksoft]

Have you tried to view the source of the page
_________________
There's someone in my head but it's not me - Pink Floyd

[OdinsDream]

Well, the thing is, Konqueror didn't print out the PHP errors. So, it was difficult to trace the problem until I opened the page in Internet Explorer, where the PHP errors and warnings were printed inline (as they should be...)

After I saw the errors, with the line numbers, I then took a look at the source-code, and traced the problem to a mySQL permissions issue. Problem solved.