I recently rebooted the server and started apache only to get a failure. Here's
the diagnosis; I'm not sure what to make of it.
systemctl status apache2.service
● apache2.service - The Apache Webserver
Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled; vendor
preset: disable
d ssl certificates recently.
JMN
> On 30 May 2022, at 7:01, Yehuda Katz wrote:
>
> systemd doesn't know to look in the HTTPD log file. What does that log say?
> Likely located in /var/log/apache2/
>
> - Y
>
> On Mon, May 30, 2022 at 9:58 AM jnil...@jala.com <ma
Yep! One of the virtual hosts has a private key/certificate mismatch. I'll try
shutting it down temporarily to see if that fixes the apache2 start problem.
> On 30 May 2022, at 8:51, Yehuda Katz wrote:
>
> Then something is probably wrong with the contents of one of your SSL
> certificates. Ma
has a separate error log.
>
> - Y
>
> On Mon, May 30, 2022 at 11:03 AM jnil...@jala.com <mailto:jnil...@jala.com>
> mailto:jnil...@jala.com>> wrote:
> The tail end of /var/log/apache2/error_log gives:
>
> [Fri May 27 00:02:10.914649 2022] [ssl:warn] [pid 1562
I'm using SUSE Leap 15.3 and apache2. I'm trying to get SSL to work on two
hosts with the same IP address. My vhosts.config is set for the two hosts but
only one actually runs. When I run systemctl status apache2.service I get a
message that NameVirtualHost has no effect and will be removed. S
d be using Leap 15.4, it
> sounds like you are out of date, sorry to say.
>
>
>
> If you go to your httpd.conf file then you will notice that there is a
> enable virtual hosts #include virtual hosts.conf httpd-vhosts.conf so
> uncomment it remove the #
>
>
orking on that.
Jack
> On 2 Jul 2022, at 1:21, Frank Gingras wrote:
>
> What does the error log say, exactly? Note that TLS failures can be almost
> silent in the logs, so if a single vhost causes the startup error, then check
> the certificate.
>
> On Fri, 1 Jul 20
