Continuing the discussion from About the Help category:
Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is: ingber.com
I ran this command: certbot -d ingber.com -d www.ingber.com
It produced this output:
My web server is (include version):
apache2 version 4.0.0
The operating system my web server runs on is (include version):
apache2 4.0.0
My hosting provider, if applicable, is: Linode
I can login to a root shell on my machine (yes or no, or I don't know):
yes
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
No
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
certbot 4.0.0
Note: I have used this command to certbot previously.
Your site --- http://ingber.com` is serving content over HTTP that includes hundreds of links and assets pointing to https:// — but it does not redirect HTTP to HTTPS.
Header always set Strict-Transport-Security "max-age=63072000; includeSubDomains; preload"
In addition:
Your server at ingber.com is listening on port 443, which tells browsers and tools to expect a secure HTTPS connection.
But it responds with unencrypted HTTP.
This breaks TLS handshakes and triggers errors like “wrong version number” in curl and SSL scan tools.
It’s misleading and non-compliant with HTTPS expectations, and the correct fix is to serve proper TLS on port 443 or close it entirely if you don’t intend to support HTTPS.
This is an invalid apache vhost configuration and outside the scope of this forum.