Issue with dnsChallenge about home-assistant-addons HOT 6 CLOSED

According to the LEGO documentation it seems you are using the wrong configuration for your private key file. Your current configuration points to the path of the private key file, but you are trying to point at a file. However this can easily be fixed:

The environment variable names can be suffixed by _FILE to reference a file instead of a value. More information here.

So your configuration should probably be something like this:

log_level: DEBUG
access_logs: true
forwarded_headers_insecure: true
dynamic_configuration_path: /config/traefik/
letsencrypt:
  enabled: true
  email: [email protected]
  challenge_type: dnsChallenge
  provider: transip
env_vars:
  - TRANSIP_ACCOUNT_NAME=redacted
  - TRANSIP_PRIVATE_KEY_FILE=/config/traefik/transip.key

Notice the small difference in the env_vars? That should probably fix it. Otherwise you could also probably get away with: - TRANSIP_PRIVATE_KEY_FILE=/config/traefik/.

I also tried messing around with the environment variables to ensure that all works correctly:

log_level: INFO
access_logs: false
forwarded_headers_insecure: true
dynamic_configuration_path: /config/extras/traefik
letsencrypt:
  enabled: true
  email: [email protected]
  challenge_type: dnsChallenge
  provider: cloudflare
env_vars:
  - CF_DNS_API_TOKEN=some-cf-api-token
  - SECOND_ENV_VAR=some_value

$ printenv
HOSTNAME=32de6d38-traefik
PWD=/
TZ=Europe/Amsterdam
HOME=/root
LANG=C.UTF-8
__BASHIO_BIN=/usr/lib/bashio/bashio
CF_DNS_API_TOKEN=some-cf-api-token
SECOND_ENV_VAR=some_value
HASSIO_TOKEN=long-hex-string
TERM=xterm
SUPERVISOR_TOKEN=long-hex-string
SHLVL=2
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
_=/bin/printenv

But it seems it does work correctly. Also switching around the environment variables doesn't make a difference. Both are picked up correctly by the add-on. So my guess it's the small difference in configuration on your side.

Please let me know if this fixes your issue.

from home-assistant-addons.

@GoSpursGoNL Did my post above help you solve your issue?

from home-assistant-addons.

For the moment I switched to DuckDNS. Hopefully this weekend I can test your addon again.

from home-assistant-addons.

Unfortunately still the same error, thanks for thinking along though Alex. I'll stick with duckdns for the moment since it also has handy dynamic dns functionality.

from home-assistant-addons.

@GoSpursGoNL
I'm sorry you couldn't get it to work. I would like to see which configuration you have tried to use. Perhaps that could help me with future issues. Otherwise I'm still happy to help you out if you want.

from home-assistant-addons.

I used the configuration you provided, the error was the same. But for the moment I am happy with duckdns. Have a good weekend!

from home-assistant-addons.