letsdnsocloud: Addon dying without log output

[gdude2002]

Pretty much as the title says - The addon container is stopping every so often, without an error available in the log viewer on the hassio addon page. I'm not even really sure of the timing - I'll start it again, and then the next day I'll find out that the IP address of my instance hasn't been updated on Cloudflare, and that the addon has been stopped.

Of course, I have hassio set to start the addon on boot.

Versions

• letsdnsocloud: 1.1
• Supervisor: 150
• HassOS: 2.10 (production)
• Home Assistant: 0.90.1

I'm running this on a current model Raspberry Pi 3, dedicated to hassio. I have portainer installed, if it'd help you debug. Not sure what else I can give you, but let me know if you need more.

[PhrantiK]

Happening on mine too - I'll try to see what's up when I have time.

[gdude2002]

Gotcha, no worries. I got around it by automating a restart of the addon every hour for now, so no big rush for us!

[slipx06]

Same error here. seems to crash frequently

My workaround:

docker run -dit --restart unless-stopped

[cbrherms]

Getting the same here. I'll see if i can do any digging myself too

[PhrantiK]

Any help would be super appreciated.

[cbsplinter]

HassOS 2.12 (production)
letsdnsocloud 1.1
Supervisor 164
Home Assistant 0.93.1

I carefully followed the installation guide but when it comes time to starting the addon via the hassio dashboard, I click start but no log output is generated. When I refresh the page I see that the addon is not running. It seems to be either crashing at startup, or not executing to begin with.

I have read reports of people having trouble like this and resolving it by deleting their certs, only this is a fresh install and I have not been able to successfully generate any certs.

EDIT: I have resolved this by adding an A record to my cloudflare account. I added homeassistant.example.com whereas before I was attempting to change the A record on example.com

[megaturba]

Hi, the same problem on HassOS 4.12, any solution to automate restart for HassOS?

[MRobi1]

Problem persists on HassOS 4.13

In the logs I get
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[cmd] /run.sh exited 7
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

My certs are still good from July when this worked, but they expire in October so hopefully a fix is coming soon.