HASSIO not working anymore, not sure what it is

Installation Home Assistant OS
1

Receiving all sorts of errors in log

2018-01-02 16:21:19 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=persistent_notification.invalid_config, old_state=<state persistent_notification.invalid_config=notifying; title=Invalid config, message=The following components and platforms could not be set up:

 - [http](https://home-assistant.io/components/http/)
 - [api](https://home-assistant.io/components/api/)
 - [websocket-api](https://home-assistant.io/components/websocket_api/)
 - [system-log](https://home-assistant.io/components/system_log/)
 - [frontend](https://home-assistant.io/components/frontend/)
 - [history](https://home-assistant.io/components/history/)
 - [config](https://home-assistant.io/components/config/)
 - [media-player](https://home-assistant.io/components/media_player/)
 - [camera](https://home-assistant.io/components/camera/)
 - [logbook](https://home-assistant.io/components/logbook/)
 - [google-assistant](https://home-assistant.io/components/google_assistant/)
 - [panel-iframe](https://home-assistant.io/components/panel_iframe/)
 - sensor.history_stats
 - [zwave](https://home-assistant.io/components/zwave/)
 - [conversation](https://home-assistant.io/components/conversation/)
 - [cloud](https://home-assistant.io/components/cloud/)
 - [tts](https://home-assistant.io/components/tts/)
2

not sure where to look for

3

in chrome I receive this

Impossibile raggiungere il sito
Connessione negata da 192.168.1.12.
Cerca 192 168 8123 con Google
ERR_CONNECTION_REFUSED

4

Did you change your config?

5

Please post your config (after redacting personal information).

6

I see in this other topic you’ve been screwing up things :wink: Isn’t it easier to restore a backup?

7

I took out api_password and ssl_certificate and ssl_ley and now is working … before they were there and was working, strange

http:
  # Uncomment this to add a password (recommended!)
 # api_password: !secret api_password
 # ssl_certificate: /ssl/fullchain.pem
 # ssl_key: /ssl/privkey.pem
8

Strange, but aren’t you missing a base_url:

9

I’m sure this isn’t related. But this morning I was at work, editing some entity names etc. in the hassio configuration panel remotely via ssl and duckdns. Suddenly this afternoon I cannot get to my hassio installation remotely at all. I’ll have to check the logs when I get home but doesn’t make any sense!

10

If you make a mistake in your configuration hassio might not start. In general it’s better make sure you also have direct access to the file system when editing the configuration.

11

Sorry, to be clear. Not editing the configuration.yaml but instead using the hassio frontend. This shouldn’t have triggered a reboot or anything so it should stick be up and running as far as I can tell.

12

Perhaps this could be happening?

13

This is the same as editing the configuration.yaml. If you applied the config it might fail.

A certificate renewal fail right after you edit the config…

14

Ah, didn’t realise that, assumed it wouldn’t need a reboot. Must be that then I suppose!

15

Strangely, without any intervention from myself, it’s now up and running. Log shows no reason for shutdown, but it started at 4:17pm apparently.