On 07/06/18 21:40, wazzu62 wrote:
> read from 0x55f11344dea0 [0x55f113455ee3] (5 bytes => 5 (0x5))
> - 48 54 54 50 2fHTTP/
Here is your problem. s_client sends a TLS ClientHello to the server.
And the server responds with HTTP!!! The server is not using
I will look into the wireshark trace
Here is the output with the debug option
CONNECTED(0003)
write to 0x55f11344dea0 [0x55f11345f100] (176 bytes => 176 (0xB0))
- 16 03 01 00 ab 01 00 00-a7 03 03 8c 1a 33 4f 8e .3O.
0010 - fb e3 3f 51 82 36 ae 38-5e 86 3c af d2 82 0f d9 ..
On 07/06/18 17:57, wazzu62 wrote:
> When I run the following command on the server the reverse proxy is pointing
> to I get a similar error
> *openssl s_client -connect localhost:443*
> CONNECTED(0003)
> 140508314333632:error:1408F10B:SSL routines:ssl3_get_record:wrong version
> number:../ss
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf
> Of wazzu62
> Sent: Thursday, June 07, 2018 10:57
> Attempts to connect to the reverse proxy endpoint via a browser generate
> the following error in the apache log file
By "the apache log file", you mean the log for the
I will preface this with the fact I am not an ssl expert.
I am trying to resolve an issue I am having with apache and a reverse proxy
that I think is ssl related.
Attempts to connect to the reverse proxy endpoint via a browser generate the
following error in the apache log file
[Tue May 29 09:14:
