Secure Connection failed

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. https://crt.sh/?q=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:
https://pquirk.com

I ran this command:

It produced this output:

My web server is (include version):
Apache/2.4.38 (Raspbian)
The operating system my web server runs on is (include version):
Raspbian Buster Lite 10
My hosting provider, if applicable, is:

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):0.31.0

So I decided to replace my old server with a Raspberry Pi 4. I tried to renew my certificates, but after a couple of failed attempts I got: An unexpected error occurred:
There were too many requests of a given type :: Error creating new order :: too many certificates already issued for exact set of domains: pquirk.com: see https://letsencrypt.org/docs/rate-limits/
So I manually copied over the certificates from my old server, and that seemed to do the trick, but then I tried to set up a subdomain at cloud.pquirk.com, I tried the same trick and manually created the sub-directory for cloud.pquirk.com under /etc/letsencrypt/live and copied the keys over, but that didn’t work, so I tried certbot, and that said “live directory exists for cloud.pquirk.com” and did not work, so I deleted the directory and files I created and tried again which brought me back to the “too many requests of a given type” error and for some reason in that process my keys for pquirk.com stopped working, and all I’m left with is:
Secure Connection Failed

An error occurred during a connection to pquirk.com. SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG

I tried copying over the keys again to no avail, and now I have no idea what to try next.

Hi @pquirk

that error says: Your port 443 is a http port, not a https - port. Checking your domain there is a http answer - https://check-your-website.server-daten.de/?q=pquirk.com

Domainname Http-Status redirect Sec. G
http://pquirk.com/ 23.233.16.67 301 https://pquirk.com/ Html is minified: 100,00 % 0.283 A
http://www.pquirk.com/ 23.233.16.67 301 https://www.pquirk.com/ Html is minified: 100,00 % 0.263 A
https://pquirk.com/ 23.233.16.67 -4 0.547 W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.
https://www.pquirk.com/ 23.233.16.67 -4 0.530 W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.
http://www.pquirk.com:443/ 23.233.16.67 301 http://pquirk.com/ 0.500 Q
Visible Content:
http://pquirk.com:443/ 23.233.16.67 GZip used - 8974 / 58471 - 84,65 % 200 Html is minified: 114,95 % 2.734 Q

So the wrong combination http://pquirk.com:443/ answers.

There are a lot of new certificates:

Issuer not before not after Domain names LE-Duplicate next LE
Let’s Encrypt Authority X3 2019-10-02 2019-12-31 pquirk.com - 1 entries
Let’s Encrypt Authority X3 2019-10-02 2019-12-31 cloud.pquirk.com - 1 entries
Let’s Encrypt Authority X3 2019-10-01 2019-12-30 pquirk.com - 1 entries
Let’s Encrypt Authority X3 2019-10-01 2019-12-30 cloud.pquirk.com - 1 entries
Let’s Encrypt Authority X3 2019-10-01 2019-12-30 pquirk.com - 1 entries
Let’s Encrypt Authority X3 2019-10-01 2019-12-30 cloud.pquirk.com - 1 entries
Let’s Encrypt Authority X3 2019-09-30 2019-12-29 pquirk.com - 1 entries

and much more. Why so much? Create one certificate, then use it 60 - 85 days.

5 per week, that looks buggy.

There is an Apache.

What says

apachectl -S
1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.