• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Config issue with new Sitebuilder installation on my server?

B

benj69

Guest
Hello,

I hope you can help? ...

I have a rootserver from 1&1, with Plesk 8.4 running on it which is generally looked after by the developer. (who is currently on holiday).

I have asked him to install Sitebuilder on it, as it looks good and simple for my wife to create her websites with.

The sitebuilder (4.2) has been installed and the config file seems to look ok, but the sitebuilder wizard is still grayed out to be used in my plesk.

The sitebuilder hostname in the config file is: sitebuilder.s15300238.onlinehome-server.info
host ip = 87.106.176.134

Have you any idea what we need to change to be able to run the sitebuilder? any help is gratefully received!
Please let me also know if I can provide any further info.

thanks a lot -

Perplexed Paul :)
 
Well, it looks like some other configuration is used instead of Sitebuilder's one for domain sitebuilder.s15300238.onlinehome-server.info. You need to make sure that there is no such domain or sub-domain created in Plesk as Plesk configuration will be used instead of Sitebuilder's one.
Also, it is better to choose easier domain name for Sitebuilder in this case. Just create additional DNS record for domain so sitebuilder.domain.tld resolved properly and make configuration for Sitebuilder with help of 'sb_config' utility:

#sb_config --sb_host_ip IP_ADDRESS --sb_hostname sitebuilder.domain.tld

If you wish to make Sitebuilder accessible from Plesk also, just use following article for configuration:

http://kb.odin.com/en/5528

Hope it helps.
 
Hi Dmitry,
thanks for the info.

I have removed the domain sitebuilder.s15300238.onlinehome-server.info in Plesk.

My sitebuilder config records are now:
sb_hostname = sitebuilder.s15300238
sb_host_ip = 87.106.176.134

However, I am not quite sure though what to do, re:

it is better to choose easier domain name for Sitebuilder in this case. Just create additional DNS record for domain so sitebuilder.domain.tld resolved properly and make configuration for Sitebuilder with help of 'sb_config' utility:

#sb_config --sb_host_ip IP_ADDRESS --sb_hostname sitebuilder.domain.tld


When I run sb_config and the command:
--sb_host_ip 87.106.176.134 --sb_hostname sitebuilder.domain.tld I get the message that the command was not found.

Am I entering the wrong command? Any further help is gratefully received! - Thanks a lot Paul
 
You should run the following command:

# sb_config --sb_host_ip 87.106.176.134 --sb_hostname sitebuilder.domain.tld

or better with full path:

# /usr/local/bin/sb_config --sb_host_ip 87.106.176.134 --sb_hostname sitebuilder.domain.tld

Also, you need to make sure that domain sitebuilder.domain.tld can be resolved successfully.
 
Back
Top