cert specific config not loaded if wellknown does not exists #166

New Issue

adam · 2025-12-29T00:26:22+01:00

adam commented

2025-12-29 00:26:22 +01:00

Originally created by @Lem on GitHub (Dec 4, 2016).

Under the following circumstances certificate specific config file will not be loaded:

Using http-01 in $SCRIPTDIR/config (e.g using default config from docs/examples/config)
WELLKNOWN-dir does not exists
certificate specific config file placed in certs/domain.tld/config

root@host:/tmp# /root/dehydrated/dehydrated -c -d domain.tld
# INFO: Using main config file /root/dehydrated/config
ERROR: WELLKNOWN directory doesn't exist, please create /var/www/dehydrated and set appropriate permissions.

Even if the certificate specific config is using dns-01 it seems to be odd to enforce an existing WELLKNOWN-dir. Creating it is a simple workaround if you're using dns-01 only.

Originally created by @Lem on GitHub (Dec 4, 2016). Under the following circumstances certificate specific config file will not be loaded: - Using http-01 in `$SCRIPTDIR/config` (e.g using default config from `docs/examples/config`) - WELLKNOWN-dir does not exists - certificate specific config file placed in `certs/domain.tld/config` ``` root@host:/tmp# /root/dehydrated/dehydrated -c -d domain.tld # INFO: Using main config file /root/dehydrated/config ERROR: WELLKNOWN directory doesn't exist, please create /var/www/dehydrated and set appropriate permissions. ``` Even if the certificate specific config is using dns-01 it seems to be odd to enforce an existing WELLKNOWN-dir. Creating it is a simple workaround if you're using dns-01 only.

adam closed this issue

2025-12-29 00:26:23 +01:00

adam commented

2025-12-29 00:26:23 +01:00

@lukas2511 commented on GitHub (Dec 18, 2016):

Well this is a bit more complicated to "fix", I need to verify the config because there are parameters which may influence loading of additional config files, and I don't really want to split it up. Since the additional config files were intended to only be used in special cases I still see the requirement of the main configuration being valid.

@lukas2511 commented on GitHub (Dec 18, 2016): Well this is a bit more complicated to "fix", I need to verify the config because there are parameters which may influence loading of additional config files, and I don't really want to split it up. Since the additional config files were intended to only be used in special cases I still see the requirement of the main configuration being valid.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/dehydrated#166