SSL_ERROR_UNRECOGNIZED_NAME_ALERT #4279

elektrinis · 2025-01-08T07:41:24Z

elektrinis
Jan 8, 2025

I'm using NPM with Home Assistant, so this is HA-specific. I'm not sure what is causing the problem, so raised this question on HA forums as well.
Short story, I get an error when visiting my site: SSL_ERROR_UNRECOGNIZED_NAME_ALERT

Full story below.
I have Home Assistant OS running on proxmox VM. I have multiple web services on the server, so I’m using nginx proxy manager to forward web requests to my ha.domain.com. I have a proper static external IP address and all my websites work well. Except for HA.
I’ve configured HA to work on port 433.
I’m using Let’s Encrypt add-on to generate the keys and it finishes without errors:

[17:04:55] INFO: Selected http verification
[17:04:55] INFO: Detecting existing certificate type for ha.****.com
Saving debug log to /var/log/letsencrypt/letsencrypt.log
[17:04:57] INFO: Existing certificate using 'ecdsa' key type.
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Certificate not yet due for renewal

When I visit HA via internal IP https://192.168.69.4:433, I get an expected certificate error, which I ignore (“accept risk”) and GUI loads. I open up certificate details on Firefox and I see that the certificate is being provided, the domain is correct, it’s verified by Let’s Encrypt and that it is valid for 3 months. All seems well.

But when I visit my ha.domain.com, I get an error SSL_ERROR_UNRECOGNIZED_NAME_ALERT and there is no option to ignore it.
On certificate information, Firefox says “Verified by: Not specified”. As if no certificate is provided.

On my nginx proxy manager I’ve set to forward to HTTPS 192.168.69.4 and to port 433. NPM can supply its own certificate, but I’ve set that to off. To be clear, if I enable NPM certificate, the site loads properly. But I need proper certificate on the server itself due to other reasons, Tesla fleet integration being one of them.

Note that I have other websites on the server, they provide their own certificates, and everything is working properly with NPM certificate set to off.

Any ideas?

elektrinis · 2025-01-08T08:53:29Z

elektrinis
Jan 8, 2025
Author

Tried this in command line:

# openssl s_client -connect ha.*****.com:443
CONNECTED(00000003)
40677C4AB2790000:error:0A000458:SSL routines:ssl3_read_bytes:tlsv1 unrecognized name:../ssl/record/rec_layer_s3.c:1586:SSL alert number 112
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 7 bytes and written 320 bytes
Verification: OK

Is it possible that NPM somehow blocks my certificate?

Another weird one when trying curl:

# curl http://ha.domain.com
<!DOCTYPE html><html><head><title>Home Assistant</title><meta 
...

# curl https://ha.domain.com
curl: (35) OpenSSL/3.0.11: error:0A000458:SSL routines::tlsv1 unrecognized name

So it actually loads a document on http? I'm lost.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

SSL_ERROR_UNRECOGNIZED_NAME_ALERT #4279

{{title}}

Replies: 1 comment

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

SSL_ERROR_UNRECOGNIZED_NAME_ALERT #4279

elektrinis Jan 8, 2025

Replies: 1 comment

elektrinis Jan 8, 2025 Author

elektrinis
Jan 8, 2025

elektrinis
Jan 8, 2025
Author