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.

alias httpd.cong

Discussion in 'General Discussion' started by jdsmart, Mar 22, 2011.

  1. jdsmart

    jdsmart Registered

    Joined:
    Mar 21, 2011
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    On my last server (freebsd/apache) I hosted my own cms, that all my clients could access via theirdomain.com/myadmin . I tried adding the alias settings as they were on my old server:
    Alias /myadmin /home/sites/myadmin.domain.com/web/
    Alias /myadmin/ /home/sites/myadmin.domain.com/web/
    in the three areas in the Apache Configuration > Include editor.

    I either get nothing or 500 error messages. At this point, I am out of my depth! Do I need to change permissions/ownership of the site myadmin.domain.com - I added the sites user to the wheel group, but feel I am missing something obvious.

    Other than this minor issue, migrating 100+ sites to my new cpanel server was a breeze, and I love the cpanel interface. I have yet to find anything lacking or missing, so thank you cpanel team, I truly appreciate your work
     
  2. cPanelTristan

    cPanelTristan Quality Assurance Analyst
    Staff Member

    Joined:
    Oct 2, 2010
    Messages:
    7,623
    Likes Received:
    21
    Trophy Points:
    38
    Location:
    somewhere over the rainbow
    cPanel Access Level:
    Root Administrator
    Hello,

    What PHP handler did you have on the old machine and what PHP handler do you have on the new machine? You can find the handler in WHM > Apache Configuration > PHP and SuExec Configuration area.

    It's likely you had DSO on the old machine and are using suPHP on the new one. If that's the case, you could try changing to DSO on the new machine instead.

    Another option would be to disable FileProtect on the machine. This is an Apache module. If it is disabled, you then are not restricting users to their /home/username directories. While it would make the machine far less secure, it's the only way under suPHP to allow users to run an application outside their /home/username directory that they do not own.

    If you choose to disable FileProtect, you can run these commands to do so:

    Code:
    /scripts/disablefileprotect
    cp /usr/local/apache/conf/httpd.conf /usr/local/apache/conf/httpd.conf.bak110322
    /usr/local/cpanel/bin/apache_conf_distiller --update
    /scripts/rebuildhttpdconf
    /etc/init.d/httpd restart
    Thanks!
     
  3. jdsmart

    jdsmart Registered

    Joined:
    Mar 21, 2011
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    Wow - what a fast response! Thank you so much.
    Alas I do not have access to the old server, and that is outside of my knowlege levels! As for the security implications, I dont think, given my clientele that it should be a problem. I will play with this and report back what I find.
    Again, thank you very much.
     
Loading...

Share This Page