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

Restart Apache after reboot?

yabado

Regular Pleskian
I am having to restart https after a reboot in order to get the virtual hosts working.
If I DON'T restart https, all I get is the system default page and NOT the individual vhost index pages.

Any idea what the problem may be?
 
Yes, I am using the AWS Marketplace instance offered by Cloudlinux.

nginx is there and needs to sometime be manually kicked as well.

Only after a reboot though, so something is not occurring correctly at init,
 
You could check the nginx - status with the command

/usr/local/psa/admin/sbin/nginxmng -s​
... and if it doesn't show "Enabled", you might want to change that with the command

/usr/local/psa/admin/sbin/nginxmng -e​
If you still experience non-starting issues after a reboot, you could investigate your nginx and apache2 logs, located at "/var/log/nginx/" and "/var/log/apache2/", to search for the reason for these issues.
 
No, nginx is enabled and not the problem.

It appears that https starts too, but needs to be restarted to pick up the virtual host settings.

After the server reboots , and I run 'apachectl restart', then everything is fine ... until the next reboot.

I don't plan on rebooting at all, but when I have to, I would like to know the init process(es) is reliable.
 
Back
Top