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: mannmade.duckdns.org
I ran this command: https://mannmade.duckdns.org
It produced this output:
This site can’t provide a secure connectionmannmade.duckdns.org sent an invalid response.
Try running Windows Network Diagnostics.
ERR_SSL_PROTOCOL_ERROR
My web server is (include version):
Apache2
The operating system my web server runs on is (include version):
Ubuntu 20.04
My hosting provider, if applicable, is:
Self-hosted
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 2.6.0
Summary:
I want to be able to reach family web pages on Apache on my Ubuntu Desktop. I did the Certbot Apache install and now I can't get into the site through DuckDns.
# This site can’t provide a secure connection
**mannmade.duckdns.org** sent an invalid response.
* [Try running Windows Network Diagnostics](javascript:diagnoseErrors()).
ERR_SSL_PROTOCOL_ERROR
I can get into the site locally. When I enter "https://192.168.1.64", I get: This server could not prove that it is 192.168.1.64; its security certificate is from mannmade.duckdns.org. This may be caused by a misconfiguration or an attacker intercepting your connection. and the browser drops into http:
This might be due to Apache being configured to provide HTTP instead of HTTPS on port 443.
This makes sense, as the IP address wouldn't be part of the certificate.
It actually doesn't: it still shows https:// in the address bar. Just with a big warning that it isn't secure due to the aforementioned IP/hostname mismatch.
That said, I have a lot of trouble connecting to your website, as a large part of the DuckDNS nameservers seem to be unresponsive. See e.g. mannmade.duckdns.org | DNSViz.
But if I hardcode your IP address 173.76.164.94 to the hostname in /etc/hosts, I see that your Apache is currently not listening at port 443 at all. While port 80 works fine, connecting on port 443 results in a connection refused.
You can run sites on different ports that you choose, so for instance https://<yourdomain>:8443/ could forward to port 443 on your other server. The port 80/port 443 stuff used for http and https is just the default convention, but you can use pretty much whatever you choose as long as that what's in your configuration and you specify it in the URL when accessing the service.
Not sure if it's already mentioned by certs from Let's Encrypt can't be for IP addresses, so you need to use fully qualified dns hostnames when accessing these services via https with an LE cert.
