Lets Encrypt fails to start

Configuration
1

After upgrading to core-2021.8 my Lets Encrypt adon has failed to start.

I am not sure why and I do not know how to search for the error. I have not installed any new add-ons or anything.

If anyone can me a hint where to look or what to do, I would really appreciate it :slight_smile:

From Supervisor log:

21-08-10 08:07:04 ERROR (SyncWorker_5) [supervisor.docker] Can't start addon_core_letsencrypt: 500 Server Error for http+docker://localhost/v1.41/containers/0e33681e4486c12865ea12857fbfaba7f5b59dc061f5171038742bfc55844146/start: Internal Server Error ("driver failed programming external connectivity on endpoint addon_core_letsencrypt (8931540a60b99ddab025b3b91a72797246db26116561d20acececef9469949d2): Error starting userland proxy: listen tcp4 0.0.0.0:8123: bind: address already in use")

From the log:

Logger: homeassistant.components.hassio
Source: components/hassio/websocket_api.py:109
Integration: Home Assistant Supervisor (documentation, issues)
First occurred: 8.24.52 (1 occurrences)
Last logged: 8.24.52

Failed to to call /addons/core_letsencrypt/start - Port '8123' is already in use by something else on the host.

Core version: core-2021.8.5
Supervisor version: supervisor-2021.06.8

2

Did you change the network settings?
I believe this should stay on 80/tcp => 80 since Let’s Encrypt only works on that port
If you try to assign 8123 as port there, it is in use by HA itself.
That network port is only for Let’s Encrypt renewal and requests nothing else.
image

For completeness, this is my configuration in the options:

email: [email protected]
domains:
  - mypublicid.synology.me
certfile: fullchain.pem
keyfile: privkey.pem
challenge: http
dns: {}

After I start the addon, it stops automatically, then you can renew HA on https and the same port

3

No, I did not change anything. Have just verified the network settings. They are fine.

My configuration:

email: [email protected]
domains:
  - xxxxx.duckdns.org
certfile: fullchain.pem
keyfile: privkey.pem
challenge: http
dns: {}

image

I’ll try to change the http port later today.

4

You don’t need to (and should not) install the lets-encrypt addon if you are using DuckDNS. It is included when you set the DuckDNS addon configuration option:

lets_encrypt:
  accept_terms: true
5

You are right. Worked.

Thanks :smiley:

6

I know this is old but I’m new to HA and facing this same issue. The configuration documentation for DuckDNS addon does not show where or how to add lets_encrypt to configuration.yaml. I just copied and pasted it in there under the existing duckdns part… Posting this to help other beginners feeling overwhelmed at the initial process of getting a SmartThings integration up and running…

1 Like