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.


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

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.

Hi @calumryan,

503 errors are normally related to errors on an application being served or a configuration error. It should be on Apache’s error log. I would assume it just gets lost in it and that’s why you can’t find it.

What I’ll recommend is using something like swatchdog This should monitor the logs for you.

To fix the problem most probably you’ll need to tweak Apache however first you’ll need to pinpoint the exact error in your log. Except the above, I can’t provide you with any solution as we don’t know the exact cause of the error.

As soon as you have an error, we can act on it further.

Regards, KDSys