DirectAdmin

Method 1:

Login keys functionality is turned off in DirectAdmin. Make sure that it is enabled in the following files:

1. edit file /usr/local/directadmin/conf/directadmin.conf and make sure that line login_keys=1 is added. Add it if needed and save file;
2. edit file /usr/local/directadmin/data/users/admin/user.conf and make sure that line login_keys=ON is added. Add it if needed and save file.
3. re-install the plugin by this instruction

Open website builder from DirectAdmin and try to publish the website. If it still does not work, then continue to method 2.

Method 2:

Create login key manually:

1. Log in to DirectAdmin admin account
2. Navigate to /CMD_LOGIN_KEYS in your panel (you can enter this URL manually in address bar)
3. Click on "Create new Login Key"
4. Fill in key name: "siteprobuilder", key value: [think of some 16-char code], expires: never, uses: 0, clear key: checked, allow htm: checked, commands: CMD_LOGIN and CMD_PLUGINS.
5. Enter password below and click "Create".
   If this operation succeeds, create a new file if it doesn't exist already:
   /usr/local/directadmin/plugins/siteprobuilder/include/login_key and put there a key value you used in login key creation. Save the file.
   Afterwards, if everything succeeded, publishing to this server should start working.

Method 3:

Make sure that IP of used website builder server is not blacklisted in DirectAdmin. Make sure that IP is not listed in list of blocked IPs in file: /usr/local/directadmin/data/admin/ip_blacklist or /usr/local/directadmin/scripts/custom/all_pre.sh (if exists).

The error appears during publication and means that your DirectAdmin server cannot resolve website builder domain. To fix this problem just add website builder domain to file "/etc/hosts" on DirectAdmin server (or make it resolvable in a different way).

Most often the problem is related to the fact that website builder that you use is running under HTTP protocol whereas DirectAdmin is running under HTTPS protocol. Since website builder in DirectAdmin Evolution skin is tried to be open in an iframe, it is blocked due to browser CORS policy and the progress is stuck on loading step.

To fix this issue you can either enable HTTPS protocol for website builder (for more details on how to do this, please refer to this FAQ: Run website builder under HTTPS protocol) or update Site.pro plugin on DirectAdmin by our DirectAdmin plugin documentation.

If you get this error during publishing website, it means that DirectAdmin server could not extract some website files from zip due to some reason. Here are common reasons why this can happen:

• Earlier it could happen due to outdated website builder plugin on DirectAdmin. In rare cases it failed extracting specific files. Make sure that the plugin version on your server is not old. You can see your version on page "Plugin Manager" page, and the latest plugin version available on Site.pro here (most probably you will also see it in DirectAdmin). If they do not match, we recommend you to update plugin and check if it solves the problem with publication.
• There is not enough space on DirectAdmin server disk. This reason is most likely if you get the error randomly on every website. Obviously, to fix this problem free up some space on DirectAdmin server disk.
• If you get this error for some specific website then the problem may be caused by exceeded quota on that DirectAdmin account. Make sure that you have enough MBytes dedicated for that account. Unfortunately, it is not easy to find out how many space is needed for the website to be published. Most of space is taken by the image gallery. If you open client's website builder, check its gallery and if you see that it has a lot of images then most probably this website will take much space when published and the reason of exceeded quota is justified.
• If none of these helped, let us know about the problem by creating a ticket and reporting about this problem.

This error means that during website archive extracting on hosting, an error occurred.

One of the common reasons is that some files on hosting are not being writable.
To fix this issue, take the following steps:

1. log in to DirectAdmin server via SSH as root;
2. navigate to website's public_html folder (usually "/home/{user}/domains/{website.com}/public_html");
3. run "chown" to fix user/group of all files and folders inside public_html
4. check if publication starts working after that.

If this did not help, follow recommendations on this page.

If you are using DirectAdmin and get this error during publication website, most probably that means that there is one or more quite large files uploaded into media library and they require a little more memory to be published. By default, there is a limit of 128M setup in DirectAdmin for PHP. To increase it, take the following steps:

1. Login to server terminal as root user;
2. Type command php --ini. One of lines in output will be:

   Loaded Configuration File: [path of php.ini file]

3. Open this file with editor: nano [path of php.ini file] (replace here "[path of php.ini file]" with your path);
4. Find needed line by pressing Ctrl+W, then typing "memory_limit" and pressing Enter;
5. Increase the value for this parameter (if it is 128M, try to increase it to 256M);
6. Save file.

After that check the publication of website again whether the error was resolved.

PHP Version 5.6 (or newer) requires a valid SSL certificate to connect.

This means that the API call will fail if the DirectAdmin SSL certificate is not valid.

To avoid any compability issues, you have two options:

1. Revert to PHP Version 5.5 if you do not have a valid SSL certificate.
2. Configure a valid SSL certificate for the DirectAdmin host.

To resolve this issue, make sure that the website builder server that you use is not blocked by firewall on your server.

We recommended to whitelist all ports: 80 and 2222 in your firewall settings.