• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved Unable to create a new domain

Hello ! The same to me !
Plesk Obsidian 18.0.21 on OVH managing already three domains.

Got access to Plesk panel's Web Sites and Domains page.
Clicked "add domain "button and properly filled the page and clicked submit button.

After a minute, got the msg: "Error: Domain Service Web not exists: domain=myNewDomain.com, id=2x" with x incrementing at each attempt.

Don't see any explanation even though this post is marked as Solved.

Thx for your help.
 
Last edited:
Hello ! The same to me !
Plesk Obsidian 18.0.21 on OVH managing already three domains.

Got access to Plesk panel's Web Sites and Domains page.
Clicked "add domain "button and properly filled the page and clicked submit button.

After a minute, got the msg: "Error: Domain Service Web not exists: domain=myNewDomain.com, id=2x" with x incrementing at each attempt.

Don't see any explanation even though this post is marked as Solved.

Thx for your help.
Do you have try to execute "plesk repair all" in ssh? Also try to update to last plesk version (at the moment, 18.0.25).
 
Hi Seb,

No, not through SSH because I don't know proper commands. (EDIT just noticed your " " so I am trying the command : "plesk repair all" on shell)

Instead, I used Fix All option through dashboard. Some problems have been solved but for
- Web and FTP servers section : no problem were solved. Instead I got these messages: (all 3 sites mentionned refer to my already set web sites)

ERROR : File not found: xxxxxx.com.conf File not found: yyyyyyyyy.info.conf File not found: zzzzzzz.com.conf File not found: xxxxxx.com.conf File not found: yyyyyyyyy.info.conf File not found: zzzzzzz.com.conf

FAILED : Repairing web server configuration for all domains. This aspect can be used with individual domains ("plesk repair web example.com"), and on the server level ("plesk repair web"). httpdmng failed: Error occured while sending feedback. HTTP code returned: 429 Error occured while sending feedback. HTTP code returned: 429 Execution failed. Command: httpdmng Arguments: Array ( [0] => --reconfigure-server [1] => -no-restart ) Details: [2020-04-05 20:18:28.525] ERR [util_exec] proc_close() failed ['/usr/local/psa/admin/bin/nginx-config' '-t'] with exit code [1] [2020-04-05 20:18:30.285] ERR [util_exec] proc_close() failed ['/usr/local/psa/admin/bin/nginx-config' '-t'] with exit code [1] [2020-04-05 20:18:30.952] ERR [panel] Apache config (15861107070.15602300) generation failed: Template_Exception: nginx: [emerg] unknown directive "passenger_root" in /etc/nginx/conf.d/phusion-passenger.conf:1 nginx: configuration file /etc/nginx/nginx.conf test failed file: /usr/local/psa/admin/plib/Template/Writer/Webserver/Abstract.php line: 75 code: 0 nginx: [emerg] unknown directive "passenger_root" in /etc/nginx/conf.d/phusion-passenger.conf:1 nginx: configuration file /etc/nginx/nginx.conf test failed

FAILED : Repairing server-wide configuration parameters for web servers. httpdmng failed: [2020-04-05 20:18:49.160] ERR [util_exec] proc_close() failed ['/usr/local/psa/admin/bin/nginx-config' '-t'] with exit code [1] [2020-04-05 20:18:50.692] ERR [util_exec] proc_close() failed ['/usr/local/psa/admin/bin/nginx-config' '-t'] with exit code [1] [2020-04-05 20:18:51.360] ERR [panel] Apache config (15861107270.80338000) generation failed: Template_Exception: nginx: [emerg] unknown directive "passenger_root" in /etc/nginx/conf.d/phusion-passenger.conf:1 nginx: configuration file /etc/nginx/nginx.conf test failed file: /usr/local/psa/admin/plib/Template/Writer/Webserver/Abstract.php line: 75 code: 0 Error occured while sending feedback. HTTP code returned: 429 nginx: [emerg] unknown directive "passenger_root" in /etc/nginx/conf.d/phusion-passenger.conf:1 nginx: configuration file /etc/nginx/nginx.conf test failed


-Plesk Database section, no problem were solved. Instead I got the following warrning:

WARNING : Checking the consistency of the Plesk database Inconsistency in the table 'DomainServices' for the column dom_id: No rows in the table 'domains' with = 16

Any clue to what I can do ? Thx
 
Last edited:
In SSH
Try to rename /etc/nginx/conf.d/phusion-passenger.conf file :

mv /etc/nginx/conf.d/phusion-passenger.conf /etc/nginx/conf.d/phusion-passenger.conf.bak

Then try to start nginx

service nginx start
 
I renamed the file as recommended and restarted Nginx.
Then I rerun a plesk repair all command through SSH.
It seems going not so bad (many more green [OK]...) and ended with :

Error messages:1; Warning ;1 Errors resolved :1
exit status 1


In checking web server configuration , I still get

File not found: xxxxxxxx.com.conf .............................[ERROR]

where xxxxxx.com is one of my existing web site. By any chance, using Plesk dashboard option I tried to add my new domain and again I got a pink stripped message:

Error: Domain Service Web not exists: domain=mynewdomainname.site, id=14

:(
 
Last edited:
Hello ! The same to me !
Plesk Obsidian 18.0.21 on OVH managing already three domains.

Got access to Plesk panel's Web Sites and Domains page.
Clicked "add domain "button and properly filled the page and clicked submit button.

After a minute, got the msg: "Error: Domain Service Web not exists: domain=myNewDomain.com, id=2x" with x incrementing at each attempt.

Don't see any explanation even though this post is marked as Solved.

Thx for your help.
Hi, to solve this problem the PLESK support intervened on my server.
Good luck
 
Back
Top