kchristensen / udm-le

Let's Encrypt support for Ubiquiti UniFi OS

MIT License

572 stars 79 forks source link

udm-le.sh initial failing with custom lego provider #34

Closed cHaos91 closed 3 years ago

cHaos91 commented 3 years ago

runnning: ./udm-le.sh initial in folder /mnt/data/udm-le returns error: /.udm-le.sh: /mnt/data/udm-le/udm-le.env: line 20: lego: not found

udm-le.env.txt

kchristensen commented 3 years ago

The issue you're seeing is because on line 20 of your environment file you're trying to call lego to issue a cert using DuckDNS as your provider, which is not technically supported in udm-le.

This isn't to say that it couldn't be, but what you're attempting isn't how you'd go about implementing it.

cHaos91 commented 3 years ago

any hints on how to correctly implement this or a way to get this provider supported?

kchristensen commented 3 years ago

I'm not near a computer at the moment but changing the DNS_PROVIDER variable to duckdns and specifying the token in the env file may be all you need to do.

cHaos91 commented 3 years ago

thank you I will give that a try

kwschnei commented 3 years ago

When I set min up to work with Linode, I had to do the following. Maybe this will help.

DNS_PROVIDER='linode'
LEGO_EXPERIMENTAL_CNAME_SUPPORT=TRUE
LINODE_TOKEN=###############
LINODE_PROPAGATION_TIMEOUT=120

cHaos91 commented 3 years ago

turns out this is all i needed, perhapse we can add it to the tested and supported providers.

DuckDNS Provider

DNS_PROVIDER='duckdns' DUCKDNS_TOKEN=xxxxxx-xxxxx-xxxx-xxxx-xxxxxxxx