aarmenaa

I'm trying to set up some PHP scrips at http://chris.binarytoast.com, which is a true subdomain (not a redirect) of http://binarytoast.com/chris. Unfortunately, I keep getting HTTP 500 errors, despite hours of combing though the site via FTP chmoding files, making sure there's no PHP directives in the .htaccess, and so on. I basically started in public_html and went from there.

The weird thing is, I have a working drupal install set up at http://chris.binarytoast.com/tehclans that works perfectly. Of course, trying to access it though http://binarytoast.com/chris/tehclans makes it go off the deep end too, for some reason. But, it works, at least. So, what's going on? I can't run PHP from anywhere except that particular folder?

__________________
My server: Serva
My domain: binarytoast.com
(Yeah, yeah. I know binarytoast.com doesn't do anything.)

David

Have you contacted support about this issue?

http://desk.surpasshosting.com

__________________

aarmenaa

I suppose that'll be my next stop - I just figured I'd let the surpassers have a go at it first. Thanks.

__________________
My server: Serva
My domain: binarytoast.com
(Yeah, yeah. I know binarytoast.com doesn't do anything.)

aarmenaa

Alright, I contacted support and told them that I was having trouble with HTTP500 errors. I was also having trouble with some permissions errors - I didn't own a couple of folders for some reason. Support corrected the permission errors, but could find nothing wrong with PHPSUEXEC or PHP. However, all my PHP files now work fine!

The problem is an unexpected consequence of PHPSUEXEC: it makes sure all the owners match on PHP files and such. Because of this, if you have any file or folders you don't own (you can't delete them), PHP scripts will fail to run in every directory below your current.

In other words: If you're having trouble with PHP, get support to make sure you actually own all your files and folders (you can't change ownership yourself).

__________________
My server: Serva
My domain: binarytoast.com
(Yeah, yeah. I know binarytoast.com doesn't do anything.)

Bigjohn

Just a point to make:

If PHPSUEXEC is installed on an existing server - one where you already had stuff running with apache_php - you will almost always have to contact support for the following:
- ensure OWNERSHIP of all files is /user account
- ensure ALL FOLDERS are chmod 755
- ensure all FILES (.php/html especially) are chmod 644

Once that is done, the account should function as before.

John

__________________
Proud to be a Surmunity Mod!
XEON PASS60 PASS61
Make a fundamental difference!
My Sites:
Curious about Brewing Beer? Join the community!
>>>>> Some Change is GOOD! Keep your paycheck! Support the Fair Tax
Get into an Art museum
Victorian London
It's your brain -ON WEB - mybrainhost.com (under development)
What SHOULD Government do? Much Less than it Does!

aarmenaa

Of course, and I read about most of this. In fact, you can pretty much make sure your site is set up to work with PHPSUEXEC all on your own - a decent FTP client will allow you chmod any files you own. But that's the catch. All files should already be owned by /user, but in some cases something goes wrong and they're not. In that case, you can't chmod those files, and because PHPSUEXEC doesn't like more than one user in a directory, PHP will also fail to run.

Without PHPSUEXEC you can ignore these "stuck" files and folders (as I did), but once PHPSUEXEC is enabled it causes a world of trouble. This is the only case where it's absolutely necessary to contact support.

__________________
My server: Serva
My domain: binarytoast.com
(Yeah, yeah. I know binarytoast.com doesn't do anything.)