Login keys functionality is turned off in DirectAdmin. Make sure that it is enabled in the following files:
/usr/local/directadmin/conf/directadmin.conf - login_keys=1
/usr/local/directadmin/data/users/admin/user.conf - login_keys=ON
Update values if needed and try again.
If the problem persists after enabling login keys try to re-install the plugin following plugin installation guide.
Please try to create login key manually:
1. go to /CMD_LOGIN_KEYS in your panel (URL)
2. click on "Create new Login Key"
3. 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.
4. enter password below and click "Create".
If this operation succeeds then 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.
After that if everything is succeeded then publishing to this server should start working.
Make sure that IP of used builder server is not blacklisted in DirectAdmin. Make sure that IP is not listed in list of blocked IPs in file:
/usr/local/directadmin/scripts/custom/all_pre.sh (if exists).
PHP 5.6 or newer require a valid SSL certificate to connect. So the API call will fail if DA SSL cert is invalid. You can use PHP 5.5 to fix this problem.
Most often the problem is related to the fact that site builder which you use is running under HTTP protocol whereas DirectAdmin is running under HTTPS protocol. Since site builder in DirectAdmin Evolution skin is tried to be open in an iframe it is blocked due to browser security reasons and the progress is stuck on loading step.
To fix this issue you need to enable HTTPS protocol for site builder. Please see this page for more details on how to do this: https://site.pro/tr/Hostingler-için/SSS/#kb516.
If you get this error during publishing website then 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:
If you are using DirectAdmin and get this error during publication website then it most probably 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:
php --ini. One of lines in output will be:
Loaded Configuration File: [path of php.ini file]
nano [path of php.ini file](replace here "[path of php.ini file]" with your path)
After that check the publication of website again whether the error is gone.