Thanks for sending me that. THe information you provided confirms that PHP is running as CGI, and, while I know you did say that was what the panel said, since “weirdness” is evident in the dhapache ownership of a directory, I wanted to check.
As the previous poster indicated, the dhapache ownership suggests that when the dir was created, it was created by a process operated as the dhapache user. This is normally in effect only when PHP is run as an apache module. Have you ever had the domain set up to run PHP as anything other than cgi?
Sopmetime, when experimenting with installing stuff, if you have ever set the domain to run php as an apache module, then the program ends up “owning” the direcotries/files it creates, as user “dhapache”. Changing the domain back to run PHP as CGI will prevent this from happening in the future, but you will need to contact support to remove the old stuff that “dhapache” created (and now owns!).
I don’t know if any of this applies to you, but if you had the domain set to run PHP as a module at one time, then performed any DH “one-click” installs, DH resets your domain to run PHP as CGI. anything that was created by a program running before that occured will still be owned by dhapache.
From the control panel,–.Manage Domains–>Edit button on relevant domain, you can confirm the user that the CGI process is running as.
If that is your user, you will need to contact support to have them remove the stuff that is owned by user dhapache, and hopefully, help you figure out how that happened.