I am curious if anybody else has encountered this problem (referenced as this Github issue)? If I go into hass.io in the left panel and start the DuckDNS addon, go to overview and then back to the addon page I can see that is has stopped again.
Most of the time it is not a problem, but ever so often (daily or semi-daily) my clients lose access to the hass.io server on my Raspberry Pi 3. When that happens, I have to ssh into hass.io and restart the server. I am not entirely sure that it is related to the issue in question, but it sure seems plausible.
Do you monitor other system stats like memory, cpu use etc…?
This is not normal:
…(daily or semi-daily) my clients lose access to the hass.io server on my Raspberry Pi 3. When that happens, I have to ssh into hass.io and restart the server.
I monitor memory use and disk use, but not cpu, but they are not showing anything unusual. Disk use is at about 12% and memory at ~30%. I am using an official 2.5Amp RPi charger, so unless there is something faulty with the hardware, current shouldn’t be a problem.
The DuckDNS log show nothing, but I will also look at homeassistant.log the next time client access stops.