• 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.
  • Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Domains not added to vhosts_bootstrap.conf

V

Veidit

Guest
For some reason new domains are not added to vhosts_bootstrap.conf also no .include files with configurations are created for the new domains, only a vhost.conf file is added there by default.

The rights looks like this:
-rw-r----- 1 root apache 3140 28 nov 20.12 /usr/local/psa/admin/conf/vhosts_bootstrap.conf

The directory for the conf files for a non-working domain.
drwxr-x--- 3 root psaserv 4096 20 jan 02.52 .
drwxr-xr-x 13 root root 4096 20 jan 02.50 ..
drwxr-xr-x 2 root root 4096 20 jan 02.52 siteapp.d
-rw-r--r-- 1 root psacln 186 20 jan 02.50 vhost.conf


Our version: Parallels Panel version psa v10.0.1_build109101029.17 os_CentOS 5
 
After running /usr/local/psa/admin/bin/httpdmng --reconfigure-domain domainname.tld the include file seems to be created, but how can I have this solved for future domains?
 
This is still not solved, need to do this manually with each domain.
 
Yes, it is known issue and developers are working on it. It works fine when a domain is created via CLI with /usr/local/psa/bin/domain utility.
 
Yes, it is known issue and developers are working on it. It works fine when a domain is created via CLI with /usr/local/psa/bin/domain utility.

Is there any update on this known bug? It is a pain having this issue with Plesk.

Any possibility of having it fixed for 10.3?
 
Last edited by a moderator:
As far as I know it is still under developer's investigation and I think that fix will not be included to 10.3 version. You can try to test it on available 10.3 Preview.
 
It has been 10 months since this problem was reported. I can confirm that it has not been sorted out in latest version.

Can you please tell us if this bug is in your priority list or not.
 
Make sure that it is not symlink:

# ls -l /usr/local/psa/tmp

If you have this tmp directory as symlink to some place - it can be a reason of this problem.
 
The problem was reproduced only in cases when you have symlink for tmp directory and when you have incorrect permissions for /var/www/vhosts/<domain>/conf directory. Make sure that there is not root:root permissions. Group must be 'psaserv'. Contact support team if it not help. Most probably there are other reasons on your server and problem should be investigated directly on your server.
 
/var/www/vhosts/<domain>/conf directory is created by Plesk itself during the process of domain creation.

My skell is perfect and all domain related permissions are correct.

This problem is not for every domain that is created. It happens randomly to few domains. Similar to post #2 we have to run command manually to fix issue.

Also, we have multiple Plesk servers and this problem is present in all of them.

In post #5 you said problem is not with CLI mode. I don't know about CLI but problem is defiantly with API mode. Also, on this update this problem was a "known issue"

In post #8 you said about "under developer's investigation", what was outcome of this investigation?

Now in post #13 you want to say that this problem is specific to my server and not with Plesk 10?

Plesk 9 never had such issues.

Our biggest mistake was to use Plesk 10 and now it seems as if choosing Plesk itself was a blunder.
 
In post #8 you said about "under developer's investigation", what was outcome of this investigation?
As I wrote before developers have found only two reasons of this issue - tmp as symlink and wrong permissions of conf directory. Most probably there are another reasons in your case. It should be investigated and reproduced on your server. Therefore I suggest you contact Support Team because only supporters can login to your server and perform necessary investigation. If they found that it is really bug - it will be forwarded to developers.
Sorry but I can't perform this investigation only by forum's discussion in this thread - I'm not supporter.
 
Back
Top