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

New domains directed to Plesk default page

C

Captaffy

Guest
Whenever a new domain is created in Plesk, and it is accessed, either through the actual domain or Site Preview, the default Plesk page is displayed.

This is the Pleskâ„¢ default page

If you see this page it means:

1) hosting for this domain is not configured
or
2) there's no such domain registered in Plesk.

I have to restart Apache before it will display the contents of the domain's root properly. Does anyone know how to fix it so that I do not have to manually restart Apache each time?
 
Apache is not restarted immediately by default, but apache restart is required in this situation to update configuration files. I can suggest you to decrease 'Apache restart interval' in Plesk admin CP -> Server -> Server preferences section.
It was implemented to avoid too many apache restarts if a lot of operations are done in Plesk CP. It doesn't mean that apache will be restarted every time of this period. If no one makes changes in Plesk CP then apache will not be restarted, but if someone does, apache will be restarted not more often than once in the apache restart interval.
 
Originally posted by Dmitry Frantsev
Apache is not restarted immediately by default, but apache restart is required in this situation to update configuration files. I can suggest you to decrease 'Apache restart interval' in Plesk admin CP -> Server -> Server preferences section.
It was implemented to avoid too many apache restarts if a lot of operations are done in Plesk CP. It doesn't mean that apache will be restarted every time of this period. If no one makes changes in Plesk CP then apache will not be restarted, but if someone does, apache will be restarted not more often than once in the apache restart interval.

Thank you! You are so right!

I had assumed that Apache was not being automatically restarted for some reason, but I didn't realize there was an interval between restarts.
 
Back
Top