Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
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.
Unfortunately, there is no backup/restore feature in Sitebuilder 3.2 for Windows right now but it will be added in next Sitebuilder version 4.0.
Actually, backup/restore procedure can be done manually. For the backup, following actions should be performed:
1. Create backup for Sitebuilder database.
2. Create backup for site storage directory (by default C:\Program Files\SiteBuilder\Sites)
3. Create copy of C:\Program Files\SiteBuilder\Repository\Common\PublicKey.xml
4. Decrypt sections for configuration file web.config (if these sections were encrypted). It can be done with help of the following commands:
5. Create copy of this file: C:\Program Files\SiteBuilder\Web\web.config.
For the restoration following operations should be performed:
1. Fresh Sitebuilder 3.2 installation on the server.
2. Database restoration.
3. Site content restoration.
4. Copy saved C:\Program Files\SiteBuilder\Repository\Common\PublicKey.xml into appropriate location on new installation.
5. Copy saved C:\Program Files\SiteBuilder\Web\web.config file into appropriate location on new installation.
6. Encrypt sections for configuration file we.config (if you need it). If you wish to encrypt these sections you can do it with help of the following commands:
Please remember that this process was not fully tested and I can't guarantee that everything will work correctly but I have tried this way on my test server and it seems all data and configuration have been restored successfully. Let me know how it goes on your server if you are going to test it.