The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

EasyApache - suPHP Broken?

Discussion in 'EasyApache' started by NexGenUK, May 5, 2008.

  1. NexGenUK

    NexGenUK Active Member

    Joined:
    May 7, 2004
    Messages:
    35
    Likes Received:
    0
    Trophy Points:
    6
    Hello,

    Now since the intial easyapache builds it seems to have been pretty stable, however since using it to rebuild with a newer version of PHP with suPHP - all you get now is the following error (on all PHP files)

    [Tue May 06 02:46:26 2008] [error] [client 152.78.69.140] SoftException in Application.cpp:535: Directory / is not owned by jasonauk, referer: <obscured>

    The log shows relevent errors for php based requests from all users on box.

    Build layout - standard php build (5.2.6 and 5.2.5 attempted) with suPHP - each time suPHP is listing faults with security layout - as you can tell by the error its not as if / should be owned by the user.

    Any help or feedback would be appreciated,
    Dan
     
  2. lloyd_tennison

    lloyd_tennison Well-Known Member

    Joined:
    Mar 12, 2004
    Messages:
    698
    Likes Received:
    1
    Trophy Points:
    18
    Did you ever get an answer, as I just got the same thing.
     
  3. jdlightsey

    jdlightsey Perl Developer III
    Staff Member

    Joined:
    Mar 6, 2007
    Messages:
    126
    Likes Received:
    2
    Trophy Points:
    18
    Location:
    Houston Texas
    cPanel Access Level:
    Root Administrator
    Every directory in the paths leading up to a PHP script needs to be owned by either root or the account that controls the VirtualHost.

    If / or /home is owned by an account other than root SuPHP is going to refuse to run the PHP scripts in your user's home directories.
     
  4. ispro

    ispro Well-Known Member

    Joined:
    Apr 8, 2004
    Messages:
    628
    Likes Received:
    1
    Trophy Points:
    18
    I understand that thread is old, but would like to add that most often reason is / (root path).

    Just execute:
    Code:
    chown root.root /
    
    And you are done.
     
Loading...

Share This Page