لم تترجم بعض أجزاء من هذه الصفحة، نعتذر عن الإزعاج

أسئلة وأجوبة

Error communicating with DirectAdmin server - login failed

DirectAdmin

Method 1:
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.

Method 2:
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.

Method 3:
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/data/admin/ip_blacklist or /usr/local/directadmin/scripts/custom/all_pre.sh (if exists).

DirectAdmin + SSL + PHP 5.6 = problems

DirectAdmin

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.

Zip download error (code: 0)

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

Could not connect to Hosting API

DirectAdmin
Make sure that used builder server is not blocked by firewall on your server (it is recommended to whitelist all ports: 80 and 2222).

Builder not working on Evolution skin

DirectAdmin

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/ar/للإستضافات/أسئلة-وأجوبة/#kb516.

Error "File is not open" during publication

DirectAdmin

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:

  • Earlier it could happen due to outdated builder plugin on DirectAdmin. In rare cases it failed extracting specific files. Make sure that you have not so old plugin version on your server. 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 too). 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. The most of space takes the image gallery. If you open client's builder, check its gallery and 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 then let us know about the problem by creating a ticket and reporting about this problem.