giustanca

Same exact problem as everyone in my installation too. The developer is totally absent. It would be better to delete its docker container, rather than continue to have it installed by users, who in the meantime are hacking around to figure out what's wrong. The problems have been going on for several months and there hasn't been any remedial action or even an interest from the developer. His last speech is on July 24 (more than 5 months ago).

Hello. I have installed unraid-api docker on home assistant. The GUI (192.168.x.x:3005) does not start and gives me an error. "Server error An error occurred in the application and your page could not be served. If you are the application owner, check your logs for details." This is the registry log: > [email protected] start > cross-env NUXT_HOST=0.0.0.0 NUXT_PORT=80 NODE_ENV=production node server/index.js READY Server listening on http://0.0.0.0:80 ERROR Renderer resources are not loaded! Please check possible console errors and ensure dist (/app/.nuxt/dist/server) exists. at VueRenderer.renderRoute (node_modules/@nuxt/vue-renderer/dist/vue-renderer.js:4440:17) at VueRenderer.renderRoute (node_modules/@nuxt/vue-renderer/dist/vue-renderer.js:4428:21) at async nuxtMiddleware (node_modules/@nuxt/server/dist/server.js:140:20) Any idea to understand the cause of the problem?

For me it is a very obvious unraid bug. Being a fairly widespread bug I don't think it depends on the configuration of the single machines. However I have no way to ascertain this and the help on the forum, despite the upload of the diagnostics, was null.

Thank you very much for your help after loading the diagnostics ...

The hide function never worked for me either. Each time the home assistant is restarted, the mqtt entities are all visible again, even those hidden via unraid-api ui. At the moment my unraid-api does not work for the problem indicated in some post above.

Hello. I can start or stop dockers from the unraid ui. I can NOT start or stop from the api unraid ui, each attempt does not produce any effect and the content of the log is what I have already posted. Which log would you need? The diagnostic one from unraid?

Hello. I have the following problem with the unraid-api docker. Home assistant sees the dockers and unraid-api sees the mqtt (HA) broker. However, it is impossible to start any docker from Home Assistant, with the following error message contained in the log: > [email protected] start > cross-env NUXT_HOST=0.0.0.0 NODE_ENV=production node server/index.js WARN mode option is deprecated. You can safely remove it from nuxt.config Connected to mqtt broker READY Server listening on http://0.0.0.0:80 Received MQTT Topic: homeassistant/nas/clamav/dockerState and Message: started assigning ID: MQTT-R-ku2txnez Part of MQTT-R-ku2txnez failed. What is the problem? My Unraid version in 6.10.0-rc1. Thanks for help

Here is the diagnostics. Thanks for your help. nas-diagnostics-20210924-1839.zip

The problem seems common to me, I find several posts, and I don't think it depends on the configuration of the individual machines. It looks like an unraid bug

I also have the same problem: when there is a power failure the system restarts but does not enable the virtual machine service, which must be re-enabled manually. Has anyone figured out what the problem could be and therefore its solution?

Same problem here. No news to remove the "old" server from the list?

The docker works after first installation. If I restart the unraid server it stops working and won't start even if I start it manually. The unraid version is 6.8.3 and I have multiple dockers fully functional.

Hello. I have the following problem. I install the Unraid-API docker on UnRaid server and everything seems to work. Home Assistant receives data from the server. As soon as I reboot the server, the Unraid-API docker does not start and even if I start it manually it stops by itself. What could be the problem? This is the log: > [email protected] start /app > cross-env NUXT_HOST=0.0.0.0 NODE_ENV=production node server/index.js READY Server listening on http://0.0.0.0:80 Connected to mqtt broker Error: ENOENT: no such file or directory, open 'config/mqttKeys' at Object.openSync (fs.js:461:3) at Proxy.readFileSync (fs.js:364:35) at updateMQTT (/app/mqtt/index.js:268:30) at MqttClient.<anonymous> (/app/mqtt/index.js:49:7) at MqttClient.emit (events.js:327:22) at MqttClient.EventEmitter.emit (domain.js:485:12) at Readable.<anonymous> (/app/node_modules/mqtt/lib/client.js:1449:14) at Readable.emit (events.js:315:20) at Readable.EventEmitter.emit (domain.js:485:12) at endReadableNT (/app/node_modules/mqtt/node_modules/readable-stream/lib/_stream_readable.js:1010:12) { errno: -2, syscall: 'open', code: 'ENOENT', path: 'config/mqttKeys' } The secure keys for mqtt may have not been generated, you need to make 1 authenticated request via the API first for this to work Error: ENOENT: no such file or directory, open 'config/mqttKeys' at Object.openSync (fs.js:461:3) at Proxy.readFileSync (fs.js:364:35) at updateMQTT (/app/mqtt/index.js:268:30) at Timeout._onTimeout (/app/mqtt/index.js:300:5) at listOnTimeout (internal/timers.js:549:17) at processTimers (internal/timers.js:492:7) { errno: -2, syscall: 'open', code: 'ENOENT', path: 'config/mqttKeys' } The secure keys for mqtt may have not been generated, you need to make 1 authenticated request via the API first for this to work Failed to retrieve config file, creating new. ERROR ENOENT: no such file or directory, open 'config/mqttKeys' at Object.openSync (fs.js:461:3) at Proxy.readFileSync (fs.js:364:35) at default (api/getServers.js:27:36) at call (node_modules/connect/index.js:239:7) at next (node_modules/connect/index.js:183:5) at next (node_modules/connect/index.js:161:14) at next (node_modules/connect/index.js:161:14) at SendStream.error (node_modules/serve-static/index.js:121:7) at SendStream.emit (events.js:315:20) at SendStream.EventEmitter.emit (domain.js:485:12) Error: ENOENT: no such file or directory, open 'config/mqttKeys' at Object.openSync (fs.js:461:3) at Proxy.readFileSync (fs.js:364:35) at updateMQTT (/app/mqtt/index.js:268:30) at Timeout._onTimeout (/app/mqtt/index.js:300:5) at listOnTimeout (internal/timers.js:549:17) at processTimers (internal/timers.js:492:7) { errno: -2, syscall: 'open', code: 'ENOENT', path: 'config/mqttKeys' } The secure keys for mqtt may have not been generated, you need to make 1 authenticated request via the API first for this to work Get Docker Details for ip: 192.168.1.3 Failed Cannot read property 'forEach' of undefined Get Dashboard Details for ip: 192.168.1.3 Failed with status code: undefined connect ECONNREFUSED 192.168.1.3:80 Get VM Details for ip: 192.168.1.3 Failed connect ECONNREFUSED 192.168.1.3:80 Get Docker Details for ip: 192.168.1.3 Failed connect ECONNREFUSED 192.168.1.3:80 Get USB Details for ip: 192.168.1.3 Failed connect ECONNREFUSED 192.168.1.3:80 Get Main Details for ip: 192.168.1.3 Failed connect ECONNREFUSED 192.168.1.3:80 Get Dashboard Details for ip: 192.168.1.3 Failed with status code: undefined connect ECONNREFUSED 192.168.1.3:80 Get VM Details for ip: 192.168.1.3 Failed connect ECONNREFUSED 192.168.1.3:80 Get Docker Details for ip: 192.168.1.3 Failed connect ECONNREFUSED 192.168.1.3:80 Get USB Details for ip: 192.168.1.3 Failed connect ECONNREFUSED 192.168.1.3:80 Get Main Details for ip: 192.168.1.3 Failed connect ECONNREFUSED 192.168.1.3:80 > [email protected] start /app > cross-env NUXT_HOST=0.0.0.0 NODE_ENV=production node server/index.js Connected to mqtt broker READY Server listening on http://0.0.0.0:80 Get Docker Details for ip: 192.168.1.3 Failed Cannot read property 'forEach' of undefined /app/mqtt/index.js:547 let docker = server.docker.details.containers[dockerId]; ^ TypeError: Cannot read property 'containers' of undefined at ModuleContainer.getDockerDetails (/app/mqtt/index.js:547:38) at listOnTimeout (internal/timers.js:551:17) at processTimers (internal/timers.js:492:7) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! [email protected] start: `cross-env NUXT_HOST=0.0.0.0 NODE_ENV=production node server/index.js` npm ERR! Exit status 1 npm ERR! Failed at the [email protected] start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2021-01-26T11_45_32_250Z-debug.log

Report 50% used space

Hi everyone. I have the following problem with a virtual machine running Home Assistant (formerly HASSIO) on "Home Assistant OS 5.10". At the time of the creation of the virtual disk I assigned 12 GB. Initially, the installation was around 7GB. Gradually the size has grown, allocating almost all the available space. Despite the cancellation of the Home Assistant database, the space occupied does not decrease, as if the virtual machine was unable to "release" the space previously used, making it always used, reaching 100% of the virtual disk. Is there any solution to "recompact" or "free" the space that the virtual machine (or Unraid) instead indicates as used even if it is not? I don't know if I was clear enough ...