Hi Sachin,
as long as I am doing this, a non matching CN and/or v3 SubjectAlternativeNames never effected the HTTP server in a way, that it wpold stop working for me. Both messeges you quoted, ah02292 and ah01909 are warning messages. They *may* effect your client's behavior. Hence, if there is not a person in this list knowing better, this should not be of your concern.
What about that 502? This looks like your real issue to me.
However, I remember reading some stuff changed (or will change?) in regard of VirtualHost clause. But even this would not make sense, if your old certificate is still working. Next thing you could do is, look for changes int the certificate's attributes. May be there is a change, that should not be there.
Am 04.01.20 um 18:02 schrieb Sac Isilia:
> Hi Team,
>
[...]
> *502 - Web server received an invalid response while acting as a gateway or
> proxy server.*
>
> *There is a problem with the page you are looking for, and it cannot be
> displayed.*
>
> *When the Web server (while acting as a gateway or proxy) contacted the
> upstream content server, it received an invalid response from the content
> server.”*
>
> In the error logs I have found below messages .
>
> ah02292: init: name-based ssl virtual hosts only work for clients with tls
> server name indication support
>
> ah01909: rsa certificate configured for xxxxxxxxxxx:443 does not include an
> id which matches the server name
>
> Please help me in resolving this issue.
>
>
> Regards
>
> Sachin Kumar
>
Martin
|