SAN error generating cert for CNAME domain #482

Closed
opened 2025-12-29 01:26:00 +01:00 by adam · 3 comments
Owner

Originally created by @drlauridsen on GitHub (Jul 9, 2020).

Sorry if this is not the right place to ask this question, and I am a complete newbie 🙂, so this question might seem stupid..

I use nginx on my router.
I have successfully used dehydrated and generated a certificate for a subdomain supplied by asus together with my router, eg name.asuscomm.com.
I have some subdomains as CNAME on my own domain with my webhost (not my own server..) eg subd.hosteddomain.com - which then points to name.asuscomm.com.

When trying to generate certificates for these cname subdomains, I get the following error..


bash ./dehydrated --domain subd.hosteddomain.com  --cron
# INFO: Using main config file /opt/etc/nginx/config
Processing subd.hosteddomain.com
 + Signing domains...
 + Generating private key...
 + Generating signing request...
Error Loading request extension section SAN

What am I doing wrong?

Originally created by @drlauridsen on GitHub (Jul 9, 2020). Sorry if this is not the right place to ask this question, and I am a complete newbie 🙂, so this question might seem stupid.. I use nginx on my router. I have successfully used dehydrated and generated a certificate for a subdomain supplied by asus together with my router, eg name.asuscomm.com. I have some subdomains as CNAME on my own domain with my webhost (not my own server..) eg subd.hosteddomain.com - which then points to name.asuscomm.com. When trying to generate certificates for these cname subdomains, I get the following error.. ---- ``` bash ./dehydrated --domain subd.hosteddomain.com --cron # INFO: Using main config file /opt/etc/nginx/config Processing subd.hosteddomain.com + Signing domains... + Generating private key... + Generating signing request... Error Loading request extension section SAN ``` --- What am I doing wrong?
adam closed this issue 2025-12-29 01:26:00 +01:00
Author
Owner

@danimo commented on GitHub (Sep 18, 2020):

Please post the output of dehydrated --version.

@danimo commented on GitHub (Sep 18, 2020): Please post the output of `dehydrated --version`.
Author
Owner

@danimo commented on GitHub (Sep 18, 2020):

The openssl version on your asus router might be old or custom built. Can you also provide the output of openssl version and the contents of /etc/ssl/openssl.cnf (might be /etc/openssl.cnf alternatively)?

@danimo commented on GitHub (Sep 18, 2020): The openssl version on your asus router might be old or custom built. Can you also provide the output of `openssl version` and the contents of `/etc/ssl/openssl.cnf` (might be `/etc/openssl.cnf` alternatively)?
Author
Owner

@lukas2511 commented on GitHub (Dec 10, 2020):

This seems to be an issue with a weird openssl version. Seeing this as out-of-scope for dehydrated.

@lukas2511 commented on GitHub (Dec 10, 2020): This seems to be an issue with a weird openssl version. Seeing this as out-of-scope for dehydrated.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/dehydrated#482