503 error everytime on on restarting droplet
For the past couple of months I’m having 503 unavailable error following restarts. I go through several restarts to try and get it back after which it eventually recovers. I’m guessing it has something to do with my apache2 configuration though might be something else. Apache2 needs to be restarted manually each time when it does recover eventually. The apache error log though doesn’t appear to show any problems there.
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.×