Maybe the updated openssl doesn't like something about your certificates.

Does Apache have any warnings or notices when it starts up?
Try running httpd -S which lists all the vhosts Apache has and see if it
matches what you expect.
You may also see the errors from that command (tested on RHEL 7 - not quite
the same as Centos, but should be pretty close).

- Y

On Sat, Jan 16, 2016 at 3:18 PM, Ted To <t...@theo.to> wrote:

> Hi,
>
> Up until roughly a week ago, my VPS web server was working properly.
> From what I can see, the only change is that nss, nss-tools, openssl and
> gnutls were updated.  On Monday, Jan 11, I noticed that I was getting an
> SSL error when running "svn up".  When trying to open the url in a web
> browser, the page would not open but I could open it with w3m by
> accepting the certificate -- I was directed to the default CentOS apache
> start page.  The strange thing is that it only happens for a minority of
> my domains/subdomains.
>
> I am running Apache 2.4.6 on a Centos 7 box.
>
> Any thoughts/suggestions for what could be going on here?
>
> Thanks in advance!
>
> Ted To
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> For additional commands, e-mail: users-h...@httpd.apache.org
>
>

Reply via email to