Closed sholzmayer closed 4 years ago
My time is right :( These Hass.io seems very unstable. Now had this issue with another installation too :(
I'm vey disapointed with HA. the Hassbian image worked for me during the last 3 years and moving to hassio is giving me hard times on troubleshooting .. I'm also having this docker issue .. and even repair BETA dont help http://hassio/supervisor/repair: dial tcp 172.30.32.2:80: i/o timeout
:( i'm not considering move to OpenHAB but ...
:( i'm not considering move to OpenHAB but ...
You'll probably have other problems with it, I guess. No project is perfect.
I think we should fix this together and stay strong :)
Yeah, if you block ntp and the instance can refresh the time, it will not work. I can only move the startup of API before that, so you can use the cli for get logs. The time is important to work with all the SSL sites.
@Fusseldieb I have wrong time on freshly flashed hassio , cca Jan 28 2018 16:00 and there are errors - due to certificate validity -
journalctl -fu hassos-supervisor
=... certificate has expired or is not yet valid ... Fails install landingpage, retry after 60sec
... . Commanddate -s "2018-11-18 18:38"
solved my problem.
I tried several ways... and suddenly works. Maybe this take effect. My steps: (use hdmi and usb keyboard)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Not resolved at all. :( Fresh install on RPi 2 has same result. This is at 104. First time ive ever had to reset my Pi and Im totally gutted that Im in this situation.
I have the exact same issue. Date / time is correct.
Please open a new issue if you are still experiencing this.
any idea why there is no access to the service from the hassio-CLI?