• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue new domain not possible

dicker

Basic Pleskian
Server operating system version
Ubuntu 20.04.5 LTS
Plesk version and microupdate number
Plesk Obsidian Version 18.0.50 Update #1
Hello, I have a problem registering a new domain
Create physical hosting
phpinimng failed: configuration test '['/opt/plesk/php/8.1/sbin/php-fpm', '--test']' failed with code 78, and message:
[14-Feb-2023 15:50:53] ERROR: [pool customerdomain.tld] the prefix '/var/www/vhosts/system/customerdomain.tld' does not exist or is not a directory
[14-Feb-2023 15:50:53] ERROR: failed to post process the configuration
[14-Feb-2023 15:50:53] ERROR: FPM initialization failed

customerdomain.tld used to belong to a customer and was deleted by the customer. If I enter customerdomain.tld, I can add other domains.
If I remove customerdomain.tld, I cannot add any other domains either.
 
Last edited by a moderator:
Are kundendomain.tld and customerdomain.tld the same and only a translation mistake in the post? Or do they mean different domains, e.g. customerdomain.tld being the subscription and kundendomain.tld a different add-on domain?
 
Unfortunately, that was a translation error. Must always be called customerdomain.tld.
Plesk searches for customerdomain.tld when creating a new domain. But they no longer exist on the server because the customer has deleted his domain kundendomain.tld. As I said, if I enter customerdomain.tld, I can also create other domains.
 
Unfortunately, that was a translation error. Must always be called customerdomain.tld.
Plesk searches for customerdomain.tld when creating a new domain. But they no longer exist on the server because the customer has deleted his domain kundendomain.tld. As I said, if I enter customerdomain.tld, I can also create other domains.
I've edited the original post. Correct so?
 
always customerdomain.tld
I can only add other domains if the customerdomain.tld is also entered in the system. Without customerdomain.tld I can't add other domains.
 
You can try to first run
# plesk repair db -y
Watch for inconsistencies in domains. Repair will normally fix most, but sometimes the situation is too complicated for the automatic repair tool.

When no errors remain, run
# plesk repair web
afterwards.
 
After running plesk repair db -y I can create normal domains again
plesk repair web
Unknown files:
/etc/apache2/plesk.conf.d/webmails/luhost.de_webmail.conf ......... [ERROR]
Do you want to delete the configuration file? [y/n]
What should I do? y or n? Plesk seems to give a message like this for every domain. /etc/apache2/plesk.conf.d/webmails/luhost.de_webmail.conf exists
I can't delete all webmail.conf files
 
It could be good to use "Web Configurations Trouble Shooter" from the Tools & Settings page. You could remove or reconfigure selected domains, e.g. filter the luhost domain first and try it with that one to recreate the configuration files if that works. Then reconfigure all marked with errors.
 
Back
Top