I just installed Hass.io in docker on Linux but now I can´t get any Plugin to work (tested 3, all give the „500 Internal Server Error Server got itself in trouble“ - error.
I can´t find anything in the logs either, so It would be great if anyone could give a hint where to look or what to do. Ok, there´s one hint in the logs, the Log-Viewer Addon gives an error which I can´t fully understand since the missing file is existing. Anyway, this somehow hints me to the possibility that either the filesystems access rights are incorrect or some files are missing.
As a new user, somehow the board-software restricts the content, so I´ll post the logs separately.
And this is the docker container log of the ESP-Home container:
-----------------------------------------------------------
Hass.io Add-on: ESPHome
ESPHome Hass.io add-on for intelligently managing all your ESP8266/ESP32 devices.
-----------------------------------------------------------
Add-on version: 1.14.3
You are running the latest version of this add-on.
System: Ubuntu 18.04.3 LTS (amd64 / qemux86-64)
Home Assistant version: 0.103.6
Supervisor version: 195
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 10-requirements.sh: executing...
[cont-init.d] 10-requirements.sh: exited 0.
[cont-init.d] 20-nginx.sh: executing...
[cont-init.d] 20-nginx.sh: exited 0.
[cont-init.d] 30-esphome.sh: executing...
[cont-init.d] 30-esphome.sh: exited 0.
[cont-init.d] 40-migrate.sh: executing...
[cont-init.d] 40-migrate.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[19:42:34] INFO: Waiting for dashboard to come up...
[19:42:34] INFO: Starting ESPHome dashboard...
INFO Starting dashboard web server on unix socket /var/run/esphome.sock and configuration dir /config/esphome...
[19:42:35] INFO: Starting NGINX…
[/details]
Logview gives an error, but the log-file it´s complaining about is existing, so I can´t understand what´s wrong:
[details="Summary"]
events.js:201
throw err; // Unhandled 'error' event
^
Error [ERR_UNHANDLED_ERROR]: Unhandled error. ("watch for /config/home-assistant.log failed: Error: ENOENT: no such file or directory, stat '/config/home-assistant.log'")
at Tail.emit (events.js:199:17)
at Tail.watch (/usr/lib/node_modules/ws-log/node_modules/tail/lib/tail.js:97:12)
at new Tail (/usr/lib/node_modules/ws-log/node_modules/tail/lib/tail.js:81:10)
at Object.<anonymous> (/usr/lib/node_modules/ws-log/index.js:259:12)
at Module._compile (internal/modules/cjs/loader.js:959:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:995:10)
at Module.load (internal/modules/cjs/loader.js:815:32)
at Function.Module._load (internal/modules/cjs/loader.js:727:14)
at Module.require (internal/modules/cjs/loader.js:852:19)
at require (internal/modules/cjs/helpers.js:74:18) {
code: 'ERR_UNHANDLED_ERROR',
context: "watch for /config/home-assistant.log failed: Error: ENOENT: no such file or directory, stat '/config/home-assistant.log'"
}
[16:44:42] INFO: Starting Log Viewer...
2020-01-13T16:44:43.073Z logview:debug start tailing /config/home-assistant.log
events.js:201
throw err; // Unhandled 'error' event
^
Error [ERR_UNHANDLED_ERROR]: Unhandled error. ("watch for /config/home-assistant.log failed: Error: ENOENT: no such file or directory, stat '/config/home-assistant.log'")
at Tail.emit (events.js:199:17)
at Tail.watch (/usr/lib/node_modules/ws-log/node_modules/tail/lib/tail.js:97:12)
at new Tail (/usr/lib/node_modules/ws-log/node_modules/tail/lib/tail.js:81:10)
at Object.<anonymous> (/usr/lib/node_modules/ws-log/index.js:259:12)
at Module._compile (internal/modules/cjs/loader.js:959:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:995:10)
at Module.load (internal/modules/cjs/loader.js:815:32)
at Function.Module._load (internal/modules/cjs/loader.js:727:14)
at Module.require (internal/modules/cjs/loader.js:852:19)
at require (internal/modules/cjs/helpers.js:74:18) {
code: 'ERR_UNHANDLED_ERROR',
context: "watch for /config/home-assistant.log failed: Error: ENOENT: no such file or directory, stat '/config/home-assistant.log'"
}
[16:44:43] INFO: Starting Log Viewer...
2020-01-13T16:44:44.149Z logview:debug start tailing /config/home-assistant.log
events.js:201
throw err; // Unhandled 'error' event
^
Error [ERR_UNHANDLED_ERROR]: Unhandled error. ("watch for /config/home-assistant.log failed: Error: ENOENT: no such file or directory, stat '/config/home-assistant.log'")
at Tail.emit (events.js:199:17)
at Tail.watch (/usr/lib/node_modules/ws-log/node_modules/tail/lib/tail.js:97:12)
at new Tail (/usr/lib/node_modules/ws-log/node_modules/tail/lib/tail.js:81:10)
at Object.<anonymous> (/usr/lib/node_modules/ws-log/index.js:259:12)
at Module._compile (internal/modules/cjs/loader.js:959:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:995:10)
at Module.load (internal/modules/cjs/loader.js:815:32)
at Function.Module._load (internal/modules/cjs/loader.js:727:14)
at Module.require (internal/modules/cjs/loader.js:852:19)
at require (internal/modules/cjs/helpers.js:74:18) {
code: 'ERR_UNHANDLED_ERROR',
context: "watch for /config/home-assistant.log failed: Error: ENOENT: no such file or directory, stat '/config/home-assistant.log'"
}
[16:44:44] INFO: Starting Log Viewer...
2020-01-13T16:44:45.169Z logview:debug start tailing /config/home-assistant.log
2020-01-13T16:44:45.176Z logview:info listening on port 4277 (HTTP)
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing...
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[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] 00-banner.sh: executing...
-----------------------------------------------------------
Hass.io Add-on: Log Viewer
Browser-based log utility for Hass.io
-----------------------------------------------------------
Add-on version: 0.7.0
You are running the latest version of this add-on.
System: Ubuntu 18.04.3 LTS (amd64 / qemux86-64)
Home Assistant version: 0.103.6
Supervisor version: 195
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] nginx.sh: executing...
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[19:14:44] INFO: Starting Log Viewer...
[services.d] done.
2020-01-13T19:14:45.189Z logview:debug start tailing /config/home-assistant.log
2020-01-13T19:14:45.198Z logview:info listening on port 4277 (HTTP)
[19:14:45] INFO: Starting NGinx...
I just got the same error message for the first time. I am only getting it in chrome. Perhaps it is related to a chrom update. Which browser are you using?
Both edge and chrome on android work fine for me.
Edit: hard refresh did not do anything, but after figuring out I could access add-ons on another hassio install, I removed all cookies related to the site in chrome and everything works again.
Hi,
thank you for giving this hint. I just checked my installation again and now - literally without touching anything for 2 weeks - everything works. Same browser, no update. My guess: Something was stuck in the cache or so, even though I hit “reload” several times.
Sascha
When this happens to me it is usually a browser issue. In FF I click on the padlock symbol in the URL line and then click Clear Cookies and Site Data. Refresh the browser and all is well.