• Apache responding with wrong protocol

    From felix.kloft@gmail.com@21:1/5 to All on Wed Jan 31 09:47:33 2018
    I'm trying to set up Apache 2.4.25 with a Let's Encrypt certificate on Raspian Stretch. However, I can't get SSL working. Apache keeps responding with a 400 using HTTP instead of doing the SSL handshake. What's most confusing is that the log produces
    lines like:

    hostname:80 148.72.168.62 - - [31/Jan/2018:18:23:13 +0100] "\x16\x03\x01" 400 0 "-" "-"

    i.e. it says the request was coming in through port 80, even though it didn't. I changed my configuration to include 'Listen 443 https' and disabled the default listener on port 80. I made sure no process is listening on 80 and Apache is indeed bound to
    443, but it still logs port 80 and responds with 400. I tried other ports as well. I verified the requests were coming in through the right port using "sudo nc -l <port>" while Apache was stopped.

    SSLEngine is on, mod_ssl is enabled, and the paths for the certificate have been set up by certbot.

    Any help would be appreciated.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From felix.kloft@gmail.com@21:1/5 to All on Tue Feb 13 01:06:27 2018
    Solved by replacing _default_:443 with *:443 in default-ssl.conf.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From daymarakesh06@gmail.com@21:1/5 to All on Thu Apr 12 11:52:20 2018
    बुधवार, 31 जनवरी 2018 को 11:17:35 अपर UTC+5:30 को, felix...@gmail.com ने लिखा:
    I'm trying to set up Apache 2.4.25 with a Let's Encrypt certificate on Raspian Stretch. However, I can't get SSL working. Apache keeps responding with a 400 using HTTP instead of doing the SSL handshake. What's most confusing is that the log produces
    lines like:

    hostname:80 148.72.168.62 - - [31/Jan/2018:18:23:13 +0100] "\x16\x03\x01" 400 0 "-" "-"

    i.e. it says the request was coming in through port 80, even though it didn't. I changed my configuration to include 'Listen 443 https' and disabled the default listener on port 80. I made sure no process is listening on 80 and Apache is indeed bound
    to 443, but it still logs port 80 and responds with 400. I tried other ports as well. I verified the requests were coming in through the right port using "sudo nc -l <port>" while Apache was stopped.

    SSLEngine is on, mod_ssl is enabled, and the paths for the certificate have been set up by certbot.

    Any help would be appreciated.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From daymarakesh06@gmail.com@21:1/5 to All on Thu Apr 12 11:53:00 2018
    बुधवार, 31 जनवरी 2018 को 11:17:35 अपर UTC+5:30 को, felix...@gmail.com ने लिखा:
    I'm trying to set up Apache 2.4.25 with a Let's Encrypt certificate on Raspian Stretch. However, I can't get SSL working. Apache keeps responding with a 400 using HTTP instead of doing the SSL handshake. What's most confusing is that the log produces
    lines like:

    hostname:80 148.72.168.62 - - [31/Jan/2018:18:23:13 +0100] "\x16\x03\x01" 400 0 "-" "-"

    i.e. it says the request was coming in through port 80, even though it didn't. I changed my configuration to include 'Listen 443 https' and disabled the default listener on port 80. I made sure no process is listening on 80 and Apache is indeed bound
    to 443, but it still logs port 80 and responds with 400. I tried other ports as well. I verified the requests were coming in through the right port using "sudo nc -l <port>" while Apache was stopped.

    SSLEngine is on, mod_ssl is enabled, and the paths for the certificate have been set up by certbot.

    Any help would be appreciated.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)