- Why can’t I connect to haos with the domain name after 14:30 every day??
Restart the home assistant and reconnect
This is not a feature request. Moved.
Start by checking your logs.
Changing of public IP at that time?
Using ipv6 dynamic resolution. The address is also synced to the domain.It can’t connect
Restart the system to connect. After 14.30 the next day, it couldn’t be connected again
I opened two HomeasSistants with virtual machines and both had the same problem
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 nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service crond: starting
s6-rc: info: service crond successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[00:52:19] INFO: Running nginx…
- No error reported
Traceroute might help.
Is this an external domain name or the internal homeassistant.local domain name?
If it is an external one, what DNS setup translates the domain name to an IP address?
If it is external how do you keep the DNS up to date?
The script I use is real-time parsing.And it did
After the 14:30 restart, it will remain error-free until 14:30 the next day
- The external domain cannot be connected.
Use real-time script parsing
At least have the decency yo answer the questions if you are going to reply.
We have no idea of your setup. You don’t give us many clues.
Thank you for your reply. Because I don’t speak English. I machine translated all of this. I came up with a temporary solution to set up a scheduled reboot on the underlying system. Now I want to close this thread.