Job for apache2.service failed because the control process exited with error code. See "systemctl status apache2.service" and "journalctl -xe" for details.
Followed by running both of the suggested commands only to learn nada darn thing??
Here’s a few things I’ve found.
Check any new SSL Certs
Make sure any self-signed certificates are made with 2048 encryption or higher.
VirtualHost configs with errors.
Start by disabling all domains using the `a2dissite <configfile>` command and see if Apache starts.
If so, start re-enabling them with `a2ensite <config-file>` and reloading Apache until it fails. Now you’ve found your culprit.
Check the file for errors. I found it can be something as seemingly silly as putting a space between “allow, deny” vs. “allow,deny” (no space).