You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
# INFO: Using main config file /data/workdir/config
+ Account already registered!
[18:06:32] INFO: Renew certificate for domains: darcentral.theworkpc.com and aliases:
*.darcentral.theworkpc.com
# INFO: Using main config file /data/workdir/config
Processing *.customname.dynudomainsample.com with alternative names: customname.dynudomainsample.com
ERROR: Please define a valid alias for your *.customname.dynudomainsample.com wildcard-certificate. See domains.txt-documentation for more details.
When I searched for the error message, the closest one I could find in relation to it was:
which it seems that the issue was initially the add-on wasn't developed to handle wildcards but eventually fix and resolved. Since your add-on does not look for the Let's Encrypt add-on to be installed in HA, I assume that you've ported a copy of it into your code as well? Comparing the timestamps from that link to your add-on, your add-on is older than when the fix was made, so this could mean that yours does not have the capability of handling wildcards too?
I attempted to replicate the config from the link as seen below and though I didn't get an error message, I didn't get any confirmation from the logs that it was successful.
Hi,
I was trying to configure this to work with wildcard domains following the example in your documentation:
from which I get the following log:
When I searched for the error message, the closest one I could find in relation to it was:
[(https://github.com/troykelly/hassio-addons-letsencrypt-lexicon/issues/3)]
which it seems that the issue was initially the add-on wasn't developed to handle wildcards but eventually fix and resolved. Since your add-on does not look for the Let's Encrypt add-on to be installed in HA, I assume that you've ported a copy of it into your code as well? Comparing the timestamps from that link to your add-on, your add-on is older than when the fix was made, so this could mean that yours does not have the capability of handling wildcards too?
I attempted to replicate the config from the link as seen below and though I didn't get an error message, I didn't get any confirmation from the logs that it was successful.
Would appreciate if you could investigate this and hopefully get it to work. ;)
The text was updated successfully, but these errors were encountered: