Zikula Community

Hi all
Feel free to roll your eyes to heaven at this question, but I am not an expert in Apache httpd. The one thing that I know is wrong with the remote server that I am being forced to use, is that they have Apache 1.33 instead of Apache 2, in spite of my requirements list of compatible versions. They are dealing with that now, but it seems odd that the wrong Apache version could throw the DB Connection error.

For the config files, I've used PSAK to find the encrypted uname and password, and the other stuff in config and config-old seem fine, so this Apache issue is the only thing I can blame it on for now. Is this at all possible, or is the problem necessarily in one of the config files??

Thanks,
Pru

Why does this always happen to me? I tinker for days, post a question to the forums, then 10 minutes later I find the solution. Embarrassing. My config files had 'localhost' instead of the DB hostname - this was just a knee-jerk reaction from me because so many providers seem to leave the hostname as "localhost". Well, not this one.

Now if the rest of the site crashes because of Apache 1.33, I'll soon find out.

We all, to some extent or another, do it... it's just Murphy's Law. I've almost learned to ask for help early on just so I can find the answer faster myself.

Glad you worked it out. I almost, but not quite, did the same thing myself when I changed hosts a few months back.

--
Under Construction!