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

Resolved startup order of things

tkalfaoglu

Silver Pleskian
Hi. When the server restarts, I noticed that the nginx did not start. Upon examining, I found that its configuration file contained all the IP's of the system, including 10.10.0.1, which I use for the OpenVPN (it's the IP of the server).. So, if the OpenVPN server is not yet running, nginx doesn't start. Is there a way to order these startups, so that the above IP is defined before nginx tries to bind to it?

The system is a modern AlmaLinux 8.5.

Thanks!
 
Looks like you have a non-standard setup.
Your question is not really related to Plesk but more to systemd. You can set dependencies in systemd.
You may want to create a systemd drop-in for nginx and make nginx dependant on your openvpn service, example:
systemctl edit nginx.service
Then add (not tested!):
(Your OpenVPN service may have a different name, adjust it to your setup)

If this doesn't work, try this:
[Unit]
After=network-online.target remote-fs.target nss-lookup.target openvpn@server.service

Then do systemctl daemon-reload and try again

More info about systemd: systemd.unit
 
Back
Top