NAS and Bitwarden (NGNIX) can't use EC key?

[mauiboy94]

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: int.svtdenver.com

I ran this command:
sudo certbot -d *.int.svtdenver.com --manual --preferred-challenges dns certonly

It produced this output:
An RSA certificate named int.svtdenver.com already exists. Do you want to update
its key type to ECDSA?

---

(U)pdate key type/(K)eep existing key type: U
Renewing an existing certificate for *.int.svtdenver.com

My web server is (include version):

The operating system my web server runs on is (include version):Ubuntu 20.04 running docker for Bitwarden

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): certbot 2.5.0

My NAS says "invalid key" and https in Bitwarden will not load. Is EC key to blame and any way to revert back to RSA? I know EC is the way forward, but seems like not supported???? TIA

[_az]

@mauiboy94

any way to revert back to RSA

Have a look at this part of the Certbot documentation.

[mauiboy94]

Thank you so much, _az - you pointed me in the right direction, but something with my setup was awry I guess:

sudo certbot renew --key-type ecdsa --cert-name int.svtdenver.com --force-renewal gave me:

The error was: PluginError('An authentication script must be provided with --manual-auth-hook when using the manual plugin non-interactively.')

After searching the interwebs, found this gem:

sudo certbot certonly --key-type rsa --manual -d *.int.svtdenver.com:

Saving debug log to /var/log/letsencrypt/letsencrypt.log

---

An ECDSA certificate named int.svtdenver.com already exists. Do you want to
update its key type to RSA?

---

(U)pdate key type/(K)eep existing key type: U
Renewing an existing certificate for *.int.svtdenver.com

Successfully received certificate.
Certificate is saved at: /etc/letsencrypt/live/int.svtdenver.com/fullchain.pem
Key is saved at: /etc/letsencrypt/live/int.svtdenver.com/privkey.pem

Million thanks for the quick response. Your team's work is outstanding!!!!

[mauiboy94]

Just for my own edification: it does seem like particular servers (NGINX and certain NAS) don't yet like ECDSA keys? Is that a true statement? Worked like a charm after reverting back to RSA.

[_az]

nginx works with EC keys just fine.

It’s probably the NAS software/user interface that was coded to assume that RSA is the only possible key type, and that assumption was never updated.

I can think of a couple of other really popular web hosting control panels that had the same issue, for years and years.