• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Resolved Plesk bin site error when creating a domain from bash script

Im having an issue creating a domain on plesk, this command works fine when run through cli:

```plesk bin site --create newdomain.com -webspace-name existingdomain.com -www-root /httpdocs```

But when I add the same code above to a bash script (create_domain.sh) and try to run it with:

```sudo bash create_domain.sh```

I get the following error

```An error occurred during domain creation: hosting update is failed: cObject->update() failed: Some fields are empty or contain an improper value. ('www_root' = ')```

Anyone knows why this is happening?

I tried /usr/local/psa/bin/site instead of plesk bin site and I get the same issue
 
Works fine with this content of bash script:

Code:
# cat d.sh
#!/bin/sh
plesk bin site --create newdomain.com -webspace-name existingdomain.com -www-root /httpdoc

# sh d.sh
SUCCESS: Creation of domain 'newdomain.com' completed.
 
Works fine with this content of bash script:

Code:
# cat d.sh
#!/bin/sh
plesk bin site --create newdomain.com -webspace-name existingdomain.com -www-root /httpdoc

# sh d.sh
SUCCESS: Creation of domain 'newdomain.com' completed.
Thanks for getting back to me, I still get this error

An error occurred during domain creation: hosting update is failed: cObject->update() failed: Some fields are empty or contain an improper value. ('www_root' = ')var/www/vhosts/clientfunnels.io/httpdocs

Is there something wrong with my install?
 
Some fields are empty or contain an improper value.
There are many possible reasons for this error, you can check it with KB article search by this quoted phrase.
One of this reason may be a database inconsistency. Try to fix it with

# plesk repair db

Or check possible solutions from KB articles.
 
Back
Top