Question posted in
Some documentation to get you started can be found here.

Apache HTTP VM Behind HTTPS Lets Encrypt

I’ve read a lot of questions and answers which seem exactly the same as mine, but I can’t seem to get my setup to work. I have a VM running Apache with only HTTP support at 192.168.2.101:32773. I can access it on my local network as such just fine. I now am ready to expose it through my Apache web server that has Lets Encrypt setup to generate SSL certificates. So I added this to my server conf file:

<VirtualHost *:32773>
    ServerName server.com

    SSLEngine on
    SSLProxyEngine On
    SSLCertificateFile /etc/letsencrypt/live/server.com/fullchain.pem
    SSLCertificateKeyFile /etc/letsencrypt/live/server.com/privkey.pem

    ProxyRequests Off
    ProxyPreserveHost On
    ProxyPass / http://192.168.2.101:32773/
    ProxyPassReverse / http://192.168.2.101:32773/
</VirtualHost>

However, I get an ERR_SSL_PROTOCOL_ERROR when I try to load it up as https://server.com:32773. If I however change my address to http://server.com:32773, it loads just fine. Anything look wrong in this snippet? Thanks!

Tags:

2

Answers


  1. Chosen as BEST ANSWER
    0

    This is embarrassing... At some point I changed my port forward rules to point 32773 directly to 192.168.2.101 so I could validate that the rules were working at all. The above config worked as soon as I realized I wasn't even sending traffic to my Apache SSL enabled server.


  2. 0

    HTTP and HTTPS need to be on different ports. Typically HTTPS is served on port 443.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search