• 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.

Resolved were not created due to the errors in configuration templates: httpd: bad user name...

yabado

Regular Pleskian
Keep getting this error box in my panel home dashboard...

New configuration files for the Apache web server were not created due to the errors in configuration templates: httpd: bad user name example . Detailed error descriptions were sent to you by email. Please resolve the issues and click here to generate broken configuration files once again or here to generate all configuration files.

*example not actual username

I have followed all the kb articles. No errors on http -t or during reconfigure-all.

The error alert persists on the main Plesk panel dash however.

What do I need to do to fix this for good?
 
Sounds like some half removed mess. You can just add a user via the CLI;

# useradd sample

Sample being the username.
 


Here is what I have:


# grep sample /etc/passwd
sample:x:10047:503::/var/www/vhosts/sample.com:/bin/false

MariaDB [psa]> select * from sys_users where login='sample';
Empty set (0.00 sec)

Now after running adduser, I have 2 instances of the same user :-/
 
Negative, but you can reconfigure Apache successfully, and if it's not in the Plesk DB it's not a user that's needed anyways...
 

Here is what I have:


# grep sample /etc/passwd
sample:x:10047:503::/var/www/vhosts/sample.com:/bin/false

MariaDB [psa]> select * from sys_users where login='sample';
Empty set (0.00 sec)

Now after running adduser, I have 2 instances of the same user :-/

2 instances where?
 
Clear the error;

# mysql -uadmin -p`cat /etc/psa/.psa.shadow` psa
mysql > delete from Configurations where status="error";


Try rebuilding again;

# plesk repair web

See if the error comes back and/or the rebuild completes.
 
Clear the error;

# mysql -uadmin -p`cat /etc/psa/.psa.shadow` psa
mysql > delete from Configurations where status="error";


Try rebuilding again;

# plesk repair web

See if the error comes back and/or the rebuild completes.


Thanks brother. That fixed it up.

Seems that errant user was attached to a bunch of webmail configs, across several domains? weird.
 
Back
Top