DuckDNS not loading and letsenypt certificting not renewing

Installation Home Assistant OS
1

Hi, i have been struggling with this for some time now and on the brink of giving up with the secure connection, which would be a shame.

Currently the DuckDNS addon will not load, when i try i get the following result

starting version 3.2.2
# INFO: Using main config file /data/workdir/config
ERROR: Lock file '/data/workdir/lock' present, aborting.

I have tried about 10 different suggested settings for it, ltest being below from the, all though give the same error:

{
  "lets_encrypt": {
    "accept_terms": true,
    "certfile": "fullchain.pem",
    "keyfile": "privkey.pem"
  },
  "token": "xxxxxxxxxxxxx",
  "domains": [
    "xxxxxxxxx.duckdns.org"
  ],
  "seconds": 300
}

originaly the path for the .pem files was something like etc/…/letsencrypt/…/… and this worked from initial setup but since the certs expired i tried changing them, i did try etc/ssl/… as someone else had that working. Nothing solves it! I currently have the following redirects, 80 and 443 were set to 8123 but i was told i needed to move them:
80 is currently set to 80, 443 to 443, 8123 to 8123, 3218 to 3218 and 5050 to 5050

So, is the error causing the add on to abort and preventing the certs from updating or is the out of date certs causing the addon to abort? Either way how do i fix it?!

2

I don’t know exactly what’s going wrong here because the config is the same as what I use and it works great.

There shouldn’t be any problem forward ports 80 and 443 to 8123. Is any other addon using either of these ports?

3

thanks for the reply, no no other addons use these ports

just incase they affect, the other addons i have loaded are

Current Home Assistant configuration
FireTV Server
Google Assistant
Cofigurator
DuckDNS
AppDaemon

Also
Bluetooth and SSH server are installed but not running