Skip to content

Commit a0a7353

Browse files
authored
Update README to mention UNIFI_ECC_CERT environment variable (#645)
1 parent effe7c3 commit a0a7353

File tree

1 file changed

+18
-0
lines changed

1 file changed

+18
-0
lines changed

README.md

+18
Original file line numberDiff line numberDiff line change
@@ -324,6 +324,24 @@ If your certificate or private key have different names, you can set the environ
324324

325325
For letsencrypt certs, we'll autodetect that and add the needed Identrust X3 CA Cert automatically. In case your letsencrypt cert is already the chained certificate, you can set the `CERT_IS_CHAIN` environment variable to `true`, e.g. `CERT_IS_CHAIN=true`. This option also works together with a custom `CERTNAME`.
326326

327+
### Certificates Using Elliptic Curve Algorithms
328+
329+
If your certs use elliptic curve algorithms, which currently seems to be the default with letsencrypt certs, you might additionally have to set the `UNIFI_ECC_CERT` environment variable to `true`, otherwise clients will fail to establish a secure connection. For example an attempt with `curl` will show:
330+
331+
```shell
332+
% curl -vvv https://my.server.com:8443
333+
curl: (35) error:1404B410:SSL routines:ST_CONNECT:sslv3 alert handshake failure
334+
```
335+
336+
You can check your certificate for this with the following command:
337+
338+
```shell
339+
% openssl x509 -text < cert.pem | grep 'Public Key Algorithm'
340+
Public Key Algorithm: id-ecPublicKey
341+
```
342+
343+
If the output contains `id-ec` as shown in the example, then your certificate might be affected.
344+
327345
## Additional Information
328346

329347
This document describes everything you need to get Unifi-in-Docker running.

0 commit comments

Comments
 (0)