Re: [users@httpd] NameVirtualHost fails

Yes, and that config is a good compendium of bad advice and deprecated directives. El mié, 6 jul 2022 14:28, Frank Gingras escribió: > Paul, > > Not sure how your example helps with the OP issue at all. > > On Wed, 6 Jul 2022 at 06:40, Paul Kudla (SCOM.CA Internet Services Inc.) < > p...@scom.c

Re: [users@httpd] NameVirtualHost fails

Paul, Not sure how your example helps with the OP issue at all. On Wed, 6 Jul 2022 at 06:40, Paul Kudla (SCOM.CA Internet Services Inc.) < p...@scom.ca> wrote: > > this is how my ssl, vhosts, redirects are setup maybe this will help > > note any ssl website name MUST equal a valid certificate or

RE: [users@httpd] NameVirtualHost fails [EXT]

Lets encrypt is reliable from our point of view - never had an issue with it - we occasionally have issues when renewing certs - we have about 90 of them - but that is mainly with the "fake-manual" process of updating DNS which is not 100% reliable with the changes we make. In use speed should

Re: [users@httpd] NameVirtualHost fails

this is how my ssl, vhosts, redirects are setup maybe this will help note any ssl website name MUST equal a valid certificate or you will get a cert mismatch error !! granted there are several cert authorities (free ssl etc) i have found its just easier to get a resale account (lots of prov

Re: [users@httpd] NameVirtualHost fails

I've tried several variations but basically the error message is that the certificate and the key for example2.com don't match. I thought I had set up the certificate with the proper keys so something must be screwed up with the certificate. I'm working on that. Jack >

Re: [users@httpd] NameVirtualHost fails

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 2022 at 17:24, jnil...@jala.com wrote: > Here's an example version of my vhosts.conf file: > > # http redirect >

Re: [users@httpd] NameVirtualHost fails

Here's an example version of my vhosts.conf file: # http redirect ServerName central.com ServerAlias www.example1.com *.example1.com Redirect / https://www.example1.com/ ErrorLog /var/log/apache2/example1.com-error80_log CustomLog /var/log/apache2/example1.com-access80_log combined Serve

Re: [users@httpd] NameVirtualHost fails

That is one assumption, sure. Best to have the user run apachectl -S to confirm. For all we know, they could have defined invalid vhosts. On Thu, 30 Jun 2022 at 16:54, wrote: > You are missing something called virtual hosts. You are allowed one host > but you can have many virtual hosts. Secondl

RE: [users@httpd] NameVirtualHost fails

You are missing something called virtual hosts. You are allowed one host but you can have many virtual hosts. Secondly, you should 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 #

Re: [users@httpd] NameVirtualHost fails

On Thu, Jun 30, 2022 at 4:28 PM jnil...@jala.com wrote: > > 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