• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

sitebuilder installed and changed the placeholder page

qualispace

Regular Pleskian
Hello,
I had installed the demo sitebuilder module available in the Plesk Updater in the server. As a result the place holder page for all the websites has been changed. Instead of the default placeholder page, it redirects to the sitebuilder login page. Does anybody know how to restore the old setting so that there is always the placeholder page instead of the sitebuilder login page.

Regards
Nitesh
 
Check the file /etc/httpd/conf.d/sitebuilder.conf. In this file sitebuilder should answer only to sitebuilder.* requests. If the apache directives were changed, indeed your server can answer with the sitebuilder page.
 
Here is my sitebuilder.conf file, what line in this file is replacing the placeholder page with the sitebuilder install page?


#
# SiteBuilder configuration file
#
<VirtualHost ***.***.***.***:80>
ServerAdmin root@localhost
DocumentRoot /usr/local/sitebuilder
ServerName sitebuilder
ServerAlias sitebuilder.*
ErrorLog logs/sitebuilder-error_log
CustomLog logs/sitebuilder-access_log common
DirectoryIndex index.php
AddDefaultCharset UTF-8
<Directory /usr/local/sitebuilder/.keys>
Order deny,allow
Deny from all
</Directory>
<Directory /usr/local/sitebuilder/remote_admin>
AuthType Basic
Require valid-user
AuthName "Remote Administration for SiteBuilder"
AuthUserFile "/usr/local/sitebuilder/remote_admin/.htpasswd"
</Directory>
# <IfModule sapi_apache2.c>
# php_admin_flag engine on
# php_admin_value open_basedir "/usr/local/sitebuilder:/tmp"
# </IfModule>
</VirtualHost>
 
nevermind, I fixed the problem by removing sitebuilder.

#rpm -qa|grep Sitebuilder
Sitebuilder-1.1.1-rh9.<build>
#rpm -e Sitebuilder-1.1.1-rh9.<build>
 
i still have the same problem.
which line do i have to change?

thanks
 
I encountered this exact problem, and it appears to have been occuring due to the sitebuilder configuration being loaded prior to any other virtual host configuration. This in turn caused httpd to fall back on it's defined DocumentRoot for all requests not sent to a valid virtualhost.

I corrected this by moving /etc/httpd/conf.d/sitebuilder.conf to /etc/httpd/conf/sitebuilder.conf, then putting an Include directive for sitebuilder.conf in httpd.conf ( directly following the Include directive for httpd.include ). Your httpd.conf should look something like this:

Include /etc/httpd/conf/httpd.include
Include /etc/httpd/conf/sitebuilder.conf

Make this change, restart httpd, and you should be set.

- Steve
 
Back
Top