Comment 1 for bug 2009924

We couldn't reproduce this issue. Below are the steps followed:

Deploy Nagios rev 56, then SSH to it
`juju deploy nagios central-monitor --channel latest/stable --revision 56`
`juju ssh central-monitor/0`

Check the Apache service
`systemctl status apache2` # Active (Running)

Examine Apache2 error log
`cat /var/log/apache2/error.log | less`

List enabled modules
`ls /etc/apache2/mods-enabled/` or `apache2ctl -M` # access_compat is enabled by default

Configure SSL
`juju config central-monitor ssl=on`

Re-perform the above checks again.

After that, we performed the same tests on rev 58 (latest), and got the same results. Then @nkoltsov explained to us that this issue occurred in an old cloud while configuring SSL after upgrading it from Xenial to Bionic. So the overall scenario was, upgrade from Xenial to Bionic and then add SSL to Nagios.

However, we got the same result when we performed these steps and upgraded to Bionic - The access_compat module is enabled and loaded by default.