1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice

Plesk default page after psarestore

Discussion in 'Plesk for Linux - 8.x and Older' started by phoenixisp, Oct 12, 2005.

  1. phoenixisp

    phoenixisp Silver Pleskian

    27
    57%
    Joined:
    Feb 2, 2002
    Messages:
    840
    Likes Received:
    0
    Yeah, the title says it all. I have a couple of RH 9 boxes with Plesk 7.5.4 and am changing them over to CentOS 4.1. One of these servers had a small amount of data and the leasor has ssh closed. So I tried using the BU utility instead of the PMM. After the restore on the new box, everything works except for the domains showing up on the web. That may not seem like a big problem to most but ......

    Seriously, named works, the control panel works, webmail works - but on every domain the Plesk default page displays:

    This is the Pleskâ„¢ default page
    If you see this page it means:

    1) hosting for this domain is not configured
    or
    2) there's no such domain registered in Plesk.

    FTP shows all documents where they should be, and I can ping the domains from dnsstuff.com. Any ideas anyone?
     
  2. jamesyeeoc

    jamesyeeoc Guest

    0
     
    Do you have SSH on the new server?
    (I know you will have already checked some of these things)

    Check the contents of the /etc/httpd/conf/httpd.conf and .include files.

    Run the

    /usr/local/psa/admin/bin/websrvmng -u --vhost-name=domain.com

    at least on one domain, then restart Apache service and see if that has any effect.

    Did the mySQL version change between the RH9 and CentOS 4.1 ? If so, did you remember to run the utility "mysql_fix_privilege_tables" ? When going from 3.23 to 4.xx...

    Was the Plesk install on the CentOS 4.1 a 'fresh' install? If so, then is Plesk's config still set for /var/www/vhosts instead of /home/httpd/vhosts ?

    And of course, permissions and ownership of the domain docroots and subdirs, files...

    I'll post more if I think of anything else.
     
  3. phoenixisp

    phoenixisp Silver Pleskian

    27
    57%
    Joined:
    Feb 2, 2002
    Messages:
    840
    Likes Received:
    0
    Thanks for the reply James.

    It turns out that the main httpd.include AND all of the individual domains' httpd.include files are hosed. The individual domains' files still have the /home/httpd/vhosts paths instead of the /var/www/vhosts path. Plus the main httpd.include makes no reference to include each virtual host.

    Arghh!!!!!!
     
  4. phoenixisp

    phoenixisp Silver Pleskian

    27
    57%
    Joined:
    Feb 2, 2002
    Messages:
    840
    Likes Received:
    0
    OK, got it!!!

    Here's what fixed it:

    1. Create a symlink like so: #ln -s /var/www /home/httpd

    2. Go into the 'conf' directory of each domain. Every httpd.include file is now named httpd.include.new. Rename them to httpd.include

    3. Edit the /etc/httpd/conf/httpd.include file. At the end add: "Include /var/www/vhosts/domain.com/conf/httpd.include" (without the quotes of course)

    4. Restart Apache

    If Apache fails to start, check the log file (/var/log/messages) for reasons.
     
Loading...