• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Domain http directory setup issues

B

bigpete

Guest
Hope someone can help....

Just had my server reimaged and am setting up my domains again.

My issue is that when I setup a domain the httpdocs and httpsdocs directory still points to /home/httpd/vhosts/default/htdocs for the new domain.
In the past, setting domains automatically made the relevant changes to move the secure and non-secure http to /home/httpd/vhosts/domain.

Anyone have any ideas on what may be going wrong?

Cheers.
 
It looks to me like the Apache configuration doesn't include the new domains. Check:

/etc/httpd/conf/httpd.conf
/etc/httpd/conf/httpd.include
 
Yes, not sure why though. Restarting apache clears the error and it behaves with the includes.

Are the includes dynamic?
Or is there a setting in pleask to restart the apache server?

Any advice appreciated.
 
Back
Top