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!
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.
How does one check permissions, and what should they be, for SB 3.0.2 sites that fail to publish due to incorrect permissions (and how did they get incorrect anyway)?
To be able to check and understand what can be the problem first of all make sure that there are all requirements observed on publishing server. List of requirements you can find on our website here:
There is a special script which can help you to check if everything is fine with that (SITEBUILDER_ROOT/resources/publish/check.php
). It should be run from publishing site's directory. For example, if you are trying to publish to domain domain.tld you need upload this script into site's directory and run it in browser as http://domain.tld/check.php.
Before publication check.php script is uploaded into destination directory and is run from there.
Moreover, in publishing properties you set destination directory and user with the password (if it is FTP publishing mode, for example). So you need to make sure that this user has enough rights to read/write into destination folder. Also, make sure that there are no files in destination folder which are owned by 'root', for example.
Try to check it up and if you still have some issues with publishing just give me exactly error message from SiteBuilder admin CP -> Logs section.
Can't remove file 'httpdocs/attachments/Image/icon11.gif' into FTP target (httpdocs/attachments/Image/icon11.gif: No such file or directory) (publication DSN is 'FTP:nitrouswebsites@[***]:64.74.124.77::httpdocs', current site title is 'Nitrous Web Sites - Web Site Hosting, SiteBuilder Web Site Hosting, Web Site Design' , site owner is 'admin') It is possible that there are no enough permissions for writing or there is not enough free space on the server.
The error in the log is correct, in that that file does not exist. But why is that an error? Why is SiteBuilder calling for it when it does not exist, and should not exist, in the site?
The error was created by files that had been deleted in the server temporary directory (that are published to the live web server at time of publish), but there are no references in the SiteBuilder 3 site any longer to those files, so I do not understand why SiteBuilder still looks for them. In the near future for v4 release, I hope SB has a means to upload/delete files from the server that's as easy as a checkbox, like many of the other interface features in SB already.
Yes, you are right. Such situation as manual image deletion can cause described issue. Unfortunately, in Sitebuilder there is no such a feature as uploaded image deletion and if any of the images will be deleted you will get an error. This is because together with site files special file publication_list.xml is uploaded. This file contains list of files which should be uploaded. So if you delete some files manually you will need to delete them from this file also.
As I know such feature request as uploaded files deletion already exists but it will be included into Sitebuilder only after v.4 release, I guess in v.5, but can not say exactly.