[SOLVED!] Installation Issues, 500 Internal Server Error

Hi, all. I’m doing my very best not to double-post here, but I’ve been combing the forums, wiki, and Google in general trying to figure out my installation issue, all to no avail. The previous topics discussing the issue all seem to end without a solid solution. Or the provided solutions don’t solve my particular problem. Anyway, I’ll ask away now, with advance and honest apologies if I’m unknowingly breaking the rules.

Downloaded 0.9.6, six times to be exact. I started thinking I was picking up something corrupt. That appears not to be the case. On a clean install and without modifying anything, I get 500 Internal Server Error. I’ve then attempted to go through the modification steps backwards and forwards to cover all the variables, but I have not been able to get anything but the 500 Error.

The modx install is here: http://www.calvinmarty.com/modx/

My phpinfo: http://www.calvinmarty.com/phpinfo.php

My server is running Apache 5.0.27. Let me know if I’m not providing something I should be, and I’ll get it posted immediately.

I have been working through the variables backwards and forwards, modifying things based on instructions from the community. I have tried everything I could find, and every combination of those suggestions in an attempt to track down the combination that would kill the error, but I’m still stuck. I’ve ch_modded based on various sets of instructions, and in all combinations. I’ve re-named and modified, and un-modified and un-renamed the ht.access to .htaccess and back, and commented and un-commented and done all of that with every combination of ch_mod, etc..

My host is Midphase, with whom I’ve got a ticket but from whom I haven’t received a response yet. They’re very good about getting back, but the ticket’s only an hour or so old.

I’m guessing that I need to modify the php.ini, which I’ve no experience with, because it appears I need to get mod_rewrite functioning in order for ModX to work. Is this correct? The plausible explanation that I’ve concocted in my admittedly confused brain is that mod_rewrite needs to be functioning properly, but my server doesn’t want me running PHP directives in .htaccess files. It is also possible that I’m way off base and badly in need of a cocktail.

Thank you all in advance for any help you might be able to provide, and my apologies again if I should have amended this to an older post.

-Christopher Marty

mod_rewrite is an Apache feature. It is only needed if you try to use Friendly URLs, and change the ht.access to .htaccess. On a new unmodified install, this will not be an issue, as you have to use the Configuration page to set Friendly URLs on.

Thanks for the quick reply.

So, that eliminates mod_rewrite as a possible cause, which is great to know. I’ll come back and be confused about that when I start worrying about Friendly URLs.

In the meantime, I seem to be understanding, then, that I can "turn off" the .htaccess files and ignore mod_rewrite with regards to this issue, leaving me with only ch_mods?

I’m sitting on a clean install right now, with no modifications, and I’m still Captain 500 Internal.

I just got done IMing with my hosting provider, got some information, and solved my issue. So, this is for anyone out there searching desperately like I was:

500 Internal Server Error on a fresh ModX 0.9.6 Install? First thing to try, which fixed my problem:

1. Contact your hosting provider and find out if PHP is running as a service or via suExec. The fact that my server was running it via suExec was the source of my issues.

2. Then read this, and follow the instructions: http://wiki.modxcms.com/index.php/Securing_your_site. The file/folder permissions in the installation instructions for ModX do not contain the proper permissions for a server with suExec enabled. The linked article does.

3. Except, add this: ch_mod the permissions on modx/install/index.php to 755. My entire issue was caused by my server generating an error because it was not under the impression that I should be allowed to execute the file. You know, the file you have to be able to execute if you’re going to install.

Thanks for the help, and here’s hoping this comes in handy for someone.

I wonder if your FTP client has a configuration setting to set certain permissions when it uploads the files (mine does, I have it set to maintain the permissions that already exist for the files as they are uploaded)?

You know, I’ve been using Cyberduck every day for years, and I never noticed. You’re exactly right. The preferences were set to convert permissions on uploads to that of the local file or folder.

Good tip. Now to figure out why I wasn’t paying enough attention.

I use Cyberduck too. Mac rules

I solved a 500 eror by just commenting out the php_ references in .htacces so you might want to try that first.
Some hosts have things set up to that any php_ directive in .htaccess gives a 500 error.

#php_flag register_globals Off

#php_flag zlib.output_compression On
#php_value zlib.output_compression_level 5

If this solves your problem, you’ll need to make sure the Register Globals is set to Off by default or set it yourself in php.ini if possible.

Bob

@Susan:  Couldn’t agree more.  I was nine years old coding BASIC out of magazines to make Santa Claus fly across the screen, and I was a DOS and Windows user from the beginning.  Moving to Mac was about the greatest thing I ever did.  I spend most of my free time making sure everyone I know buys one.

@Bob:  You’re absolutely right in what you say, and the ModX folks have done a great job of including that in documentation and on the wiki.  It was, in fact, one of the first things I tried.  My issues were all permissions-related, though.  Confoundingly so, for a while there.

Quote from: foolgladly at Oct 01, 2007, 09:51 PM

@Susan: Couldn’t agree more. I was nine years old coding BASIC out of magazines to make Santa Claus fly across the screen, and I was a DOS and Windows user from the beginning. Moving to Mac was about the greatest thing I ever did. I spend most of my free time making sure everyone I know buys one.

@Bob: You’re absolutely right in what you say, and the ModX folks have done a great job of including that in documentation and on the wiki. It was, in fact, one of the first things I tried. My issues were all permissions-related, though. Confoundingly so, for a while there.

I wasn’t nine years old, but I did learn to program in C on the Apple II. I’ve never met anyone else who can say that. (Compiling and linking "hello world" took about 2 full minutes and it was three weeks before I got it to run).

I’ve been really lucky with permissions. I dread the day when I hit a problem like yours. Congratulations on getting it sorted.

Bob