August 24, 20241 yr I noticed the same high CPU usage after updating Unraid 6.12.10 to 6.12.13. There were plenty of connection denied errors in the logs and the connection kept connecting then failing. I saw that @BoKKeR posted a new tagged version for the container, unraidapi-re:6.12. CPU usage dropped and started reporting normally. Just want to say thank you for your efforts and contribution to this community!
September 22, 20241 yr I am running UNRAID 6.12.13 with the unraidapi-re:6.12 tagged container. The MQTT connection to Home Assistant is working but the docker console continually shows a log error when trying to find a file 'mqttDisabledDevices.json' in /config. That file doesn't exist in /config and I'm not sure what process would cause it to be written. Error: ENOENT: no such file or directory, open 'config/mqttDisabledDevices.json' at Object.openSync (node:fs:590:3) at Object.readFileSync (node:fs:458:35) at updateMQTT (/app/mqtt/index.ts:388:21) at Timeout._onTimeout (/app/mqtt/index.ts:433:5) at listOnTimeout (node:internal/timers:559:17) at processTimers (node:internal/timers:502:7) { errno: -2, syscall: 'open', code: 'ENOENT', path: 'config/mqttDisabledDevices.json' I've found the source of the code in mqtt/index.ts, line 385-392. I tried commenting out the error logging but then the container wouldn't run. Does anybody have the mqttDisabledDevices.json file in their /config directory? I've checked back through a number of old backups and that file has never been in my config. The container seems to be running fine but I'd prefer not to be using up resources with the continual error and logging.
September 27, 20241 yr On 9/22/2024 at 7:45 PM, Ludditus said: I am running UNRAID 6.12.13 with the unraidapi-re:6.12 tagged container. The MQTT connection to Home Assistant is working but the docker console continually shows a log error when trying to find a file 'mqttDisabledDevices.json' in /config. That file doesn't exist in /config and I'm not sure what process would cause it to be written. Error: ENOENT: no such file or directory, open 'config/mqttDisabledDevices.json' at Object.openSync (node:fs:590:3) at Object.readFileSync (node:fs:458:35) at updateMQTT (/app/mqtt/index.ts:388:21) at Timeout._onTimeout (/app/mqtt/index.ts:433:5) at listOnTimeout (node:internal/timers:559:17) at processTimers (node:internal/timers:502:7) { errno: -2, syscall: 'open', code: 'ENOENT', path: 'config/mqttDisabledDevices.json' I've found the source of the code in mqtt/index.ts, line 385-392. I tried commenting out the error logging but then the container wouldn't run. Does anybody have the mqttDisabledDevices.json file in their /config directory? I've checked back through a number of old backups and that file has never been in my config. The container seems to be running fine but I'd prefer not to be using up resources with the continual error and logging. Hi @Ludditus I am also using the same APi, I upgraded to 6.12.13 and have started having some issues since then. I removed the full container, directory and reinstalled but now I have some different issues, it seems to be adding a second server to the name when creating the entites, as an example my server is called US1, my entities were US1_Server, they seem to have changed to US1_Server_Server and this seems to have happened with the most recent update, as per the original post this docker is scraping the GUI so my gut is telling me some GUI changes are now causing this issue. But to answer your question regarding the error in the logs, I see the same error, I dont have that config file present either, however I did manage to go through some old backups and found that file is present. you could easily create the file, the contents of the file looks like its looking for an array of items but mines is blank (Nothing in the array) I hope this helps, I am still trying to understand why the APi on my unraid machine is now adding an additiona _Server to the end of the current _Server.
September 27, 20241 yr Author Havent had time to look into unraid 7.0.0 yet, I am having some issues rewriting the existing code base to be testable, and I am not happy with how much the container calls the unraid UI, would like to focus on testability and adding exponential backoff for fetching the UI. I will hopefully do some of the work this weekend if nothing else happens. As said before, its a new codebase for me also and I am discovering things as I go It requires quite a lot of free time to wrap my head around the code base thats why I have been more absent than usual from this project. Coupled with real life responsibilities. Hopefully we will get to a stable release cycle There is a branch I am currently working on which would require testing: 6.12-async docker tag can be pulled Edited September 27, 20241 yr by BoKKeR
September 28, 20241 yr Author I have pushed a new update to the 6.12 tag with better fetching and error handling, and have started looking into 7.0.0 which seems to work mostly out of the box on first tests. I also fixed the missing mqttDisabledJson error @Ludditus and I will look into the server naming @DeekB To enable more logging use LOG_LEVEL=debug Edited September 29, 20241 yr by BoKKeR
October 1, 20241 yr Hi, I see an weird error where it simply refuses to find the webui of the tower (I've verified that the URL is correct). I'm not using the default unraid webui port (webui is at a random port: 4123 instead of 80, and I'm reverse proxying the webui to this url): 2024-09-30 23:46:23 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:46:23 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:46:24 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:46:25 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:46:25 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:46:28 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:46:30 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:46:30 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:46:30 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:46:36 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:46:37 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:46:41 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:46:46 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:46:51 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:46:56 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:47:01 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:47:06 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:47:11 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:47:16 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:47:21 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:47:27 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:47:32 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:47:37 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:47:37 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:48:37 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:49:37 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:50:37 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:50:46 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:50:52 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:50:57 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:51:02 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:51:07 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:51:12 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:51:17 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:51:23 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:51:28 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:51:33 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:51:37 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:51:38 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:51:43 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:51:48 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:51:53 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:51:58 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:52:03 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:52:08 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:52:13 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:52:18 [error]: Failed to fetch login for http://web.tower Any ideas on how to fix this? I've attempted everything save setting the webui to 80
October 2, 20241 yr Hiya, after my docker.image starting to get big i wanted to see if i could get thge biggest containers smaller before actually increasing the size of the docker.imgae. And UnraidAPI is kinda big for me, mine is being around 1.14 GB atm. How big is normal for it and is there a way to decrease its size?
October 2, 20241 yr Author @the_lucifer try setting LOG_LEVEL to debug @ABEIDO it’s currently running in dev mode, it’s something I totally forgot about. Today I managed to build the files and rewrite the dockerfile. Yet Somehow the backend did not package properly. Once I figure it out the size will be around 370mb
October 3, 20241 yr Oct 3 13:53:03 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 13:53:28 unRAID php-fpm[13939]: [WARNING] [pool www] child 10044 exited on signal 9 (SIGKILL) after 36.075792 seconds from start Oct 3 13:53:31 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 13:53:31 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 13:54:24 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 13:56:29 unRAID php-fpm[13939]: [WARNING] [pool www] child 19460 exited on signal 9 (SIGKILL) after 178.623462 seconds from start Oct 3 13:56:30 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 13:57:21 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 14:01:55 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 14:02:02 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 14:02:06 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 14:02:07 unRAID php-fpm[13939]: [WARNING] [pool www] child 22890 exited on signal 9 (SIGKILL) after 338.009257 seconds from start Oct 3 14:02:23 unRAID php-fpm[13939]: [WARNING] [pool www] child 18067 exited on signal 9 (SIGKILL) after 252.357514 seconds from start Oct 3 14:02:32 unRAID php-fpm[13939]: [WARNING] [pool www] child 1230 exited on signal 9 (SIGKILL) after 20.989240 seconds from start Oct 3 14:02:33 unRAID php-fpm[13939]: [WARNING] [pool www] child 1242 exited on signal 9 (SIGKILL) after 26.034769 seconds from start Oct 3 14:02:41 unRAID php-fpm[13939]: [WARNING] [pool www] child 1246 exited on signal 9 (SIGKILL) after 30.356741 seconds from start Oct 3 14:02:58 unRAID php-fpm[13939]: [WARNING] [pool www] child 6489 exited on signal 9 (SIGKILL) after 31.104795 seconds from start Oct 3 14:02:59 unRAID php-fpm[13939]: [WARNING] [pool www] child 7196 exited on signal 9 (SIGKILL) after 26.949283 seconds from start Oct 3 14:03:26 unRAID php-fpm[13939]: [WARNING] [pool www] child 7283 exited on signal 9 (SIGKILL) after 43.395091 seconds from start Oct 3 14:05:22 unRAID php-fpm[13939]: [WARNING] [pool www] child 8036 exited on signal 9 (SIGKILL) after 134.774870 seconds from start Oct 3 14:05:22 unRAID winbindd[31044]: [2024/10/03 14:05:22.899294, 0] ../../source3/winbindd/winbindd.c:821(winbind_client_processed) Oct 3 14:05:22 unRAID winbindd[31044]: winbind_client_processed: request took 113.054156 seconds Oct 3 14:05:23 unRAID winbindd[31044]: [struct process_request_state] ../../source3/winbindd/winbindd.c:437 [2024/10/03 14:03:28.682842] ../../source3/winbindd/winbindd.c:618 [2024/10/03 14:05:21.736998] [113.054156] -> TEVENT_REQ_DONE (2 0)) Oct 3 14:05:23 unRAID winbindd[31044]: [struct resp_write_state] ../../nsswitch/wb_reqtrans.c:307 [2024/10/03 14:03:53.184545] ../../nsswitch/wb_reqtrans.c:344 [2024/10/03 14:05:20.052931] [86.868386] -> TEVENT_REQ_DONE (2 0)) Oct 3 14:05:23 unRAID winbindd[31044]: [struct writev_state] ../../lib/async_req/async_sock.c:267 [2024/10/03 14:03:54.557312] ../../lib/async_req/async_sock.c:373 [2024/10/03 14:03:56.157532] [1.600220] -> TEVENT_REQ_DONE (2 0)) Oct 3 14:05:24 unRAID php-fpm[13939]: [WARNING] [pool www] child 9231 exited on signal 9 (SIGKILL) after 145.563803 seconds from start Oct 3 14:05:25 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 14:05:25 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 14:34:46 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 14:51:37 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 14:51:47 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 14:51:51 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:01:02 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:03:52 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:03:54 unRAID php-fpm[13939]: [WARNING] [pool www] child 31981 exited on signal 9 (SIGKILL) after 266.539681 seconds from start Oct 3 15:04:32 unRAID php-fpm[13939]: [WARNING] [pool www] child 16194 exited on signal 9 (SIGKILL) after 252.691411 seconds from start Oct 3 15:04:32 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:04:42 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:04:45 unRAID php-fpm[13939]: [WARNING] [pool www] child 21956 exited on signal 9 (SIGKILL) after 247.796231 seconds from start Oct 3 15:04:48 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:05:07 unRAID php-fpm[13939]: [WARNING] [pool www] child 8085 exited on signal 9 (SIGKILL) after 238.418340 seconds from start Oct 3 15:05:08 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:05:08 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:05:12 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:05:22 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:07:51 unRAID php-fpm[13939]: [WARNING] [pool www] child 10529 exited on signal 9 (SIGKILL) after 319.456800 seconds from start Oct 3 15:07:54 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:07:54 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:21:54 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:22:32 unRAID php-fpm[13939]: [WARNING] [pool www] child 4049 exited on signal 9 (SIGKILL) after 260.721522 seconds from start Oct 3 15:22:35 unRAID php-fpm[13939]: [WARNING] [pool www] child 18776 exited on signal 9 (SIGKILL) after 220.744470 seconds from start Oct 3 15:22:39 unRAID php-fpm[13939]: [WARNING] [pool www] child 19035 exited on signal 9 (SIGKILL) after 224.187747 seconds from start Oct 3 15:22:41 unRAID php-fpm[13939]: [WARNING] [pool www] child 20154 exited on signal 9 (SIGKILL) after 221.831942 seconds from start Oct 3 15:22:43 unRAID php-fpm[13939]: [WARNING] [pool www] child 15357 exited on signal 9 (SIGKILL) after 143.506751 seconds from start Oct 3 15:22:44 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:22:44 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:22:45 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:22:51 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:23:06 unRAID php-fpm[13939]: [WARNING] [pool www] child 17342 exited on signal 9 (SIGKILL) after 160.627159 seconds from start Oct 3 15:23:07 unRAID php-fpm[13939]: [WARNING] [pool www] child 1171 exited on signal 9 (SIGKILL) after 32.019418 seconds from start Oct 3 15:23:12 unRAID php-fpm[13939]: [WARNING] [pool www] child 2310 exited on signal 9 (SIGKILL) after 30.522741 seconds from start Oct 3 15:23:15 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:23:15 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:23:15 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:23:30 unRAID php-fpm[13939]: [WARNING] [pool www] child 7574 exited on signal 9 (SIGKILL) after 22.658405 seconds from start Oct 3 15:23:34 unRAID php-fpm[13939]: [WARNING] [pool www] child 7626 exited on signal 9 (SIGKILL) after 25.270129 seconds from start Oct 3 15:23:37 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:23:37 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:23:37 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:23:37 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:24:51 unRAID php-fpm[13939]: [WARNING] [pool www] child 2244 exited on signal 9 (SIGKILL) after 72.725302 seconds from start Oct 3 15:24:53 unRAID php-fpm[13939]: [WARNING] [pool www] child 8682 exited on signal 9 (SIGKILL) after 100.615011 seconds from start Oct 3 15:24:55 unRAID php-fpm[13939]: [WARNING] [pool www] child 10652 exited on signal 9 (SIGKILL) after 84.060476 seconds from start Oct 3 15:24:58 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:24:58 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:30:40 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:30:45 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:31:05 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:31:59 unRAID php-fpm[13939]: [WARNING] [pool www] child 20377 exited on signal 9 (SIGKILL) after 188.958328 seconds from start Oct 3 15:32:10 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:32:11 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:32:20 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:33:06 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:33:21 unRAID php-fpm[13939]: [WARNING] [pool www] child 21962 exited on signal 9 (SIGKILL) after 270.338870 seconds from start Oct 3 15:33:22 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:33:46 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:35:11 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:36:04 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:36:05 unRAID php-fpm[13939]: [WARNING] [pool www] child 22588 exited on signal 9 (SIGKILL) after 163.178582 seconds from start Oct 3 15:36:07 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:36:11 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:36:46 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:36:56 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:37:06 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:37:16 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:37:21 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:37:36 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 15:37:47 unRAID php-fpm[13939]: [WARNING] [pool www] child 14383 exited on signal 9 (SIGKILL) after 231.745064 seconds from start Oct 3 15:37:49 unRAID php-fpm[13939]: [WARNING] [pool www] child 16719 exited on signal 9 (SIGKILL) after 233.490123 seconds from start Oct 3 15:37:49 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 16:03:25 unRAID winbindd[31044]: [2024/10/03 16:03:25.140793, 0] ../../source3/winbindd/winbindd.c:821(winbind_client_processed) Oct 3 16:03:25 unRAID winbindd[31044]: winbind_client_processed: request took 132.175998 seconds Oct 3 16:03:25 unRAID winbindd[31044]: [struct process_request_state] ../../source3/winbindd/winbindd.c:437 [2024/10/03 16:01:12.485915] ../../source3/winbindd/winbindd.c:618 [2024/10/03 16:03:24.661913] [132.175998] -> TEVENT_REQ_DONE (2 0)) Oct 3 16:03:25 unRAID winbindd[31044]: [struct resp_write_state] ../../nsswitch/wb_reqtrans.c:307 [2024/10/03 16:03:24.454491] ../../nsswitch/wb_reqtrans.c:344 [2024/10/03 16:03:24.661909] [0.207418] -> TEVENT_REQ_DONE (2 0)) Oct 3 16:03:25 unRAID winbindd[31044]: [struct writev_state] ../../lib/async_req/async_sock.c:267 [2024/10/03 16:03:24.454491] ../../lib/async_req/async_sock.c:373 [2024/10/03 16:03:24.530395] [0.075904] -> TEVENT_REQ_DONE (2 0)) Oct 3 16:03:25 unRAID php-fpm[13939]: [WARNING] [pool www] child 5889 exited on signal 9 (SIGKILL) after 277.729482 seconds from start Oct 3 16:03:27 unRAID php-fpm[13939]: [WARNING] [pool www] child 10576 exited on signal 9 (SIGKILL) after 265.738839 seconds from start Oct 3 16:03:27 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 16:03:27 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 16:05:17 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 16:05:23 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 16:08:28 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 16:08:28 unRAID webGUI: Successful login user root from 172.18.0.37 Oct 3 16:08:28 unRAID webGUI: Successful login user root from 172.18.0.37 Latest update make my server unstable, it crash every 12 hours
October 5, 20241 yr Only docker section is available, is this normal? unraid 6.12.10 Logs: ``` Failed to retrieve config file, creating new. 2024-10-05 00:27:39 [info]: Updating auth cookie for https://192.168.50.50:448 [redacted]=[redacted]; path=/; secure; HttpOnly; SameSite=Lax 2024-10-05 00:27:40 [warn]: Skipping VMs for https://192.168.50.50:448 2024-10-05 00:27:43 [warn]: Skipping VMs for https://192.168.50.50:448 2024-10-05 00:27:46 [error]: request to https://192.168.50.50:448/state/plugins/dynamix.docker.manager/images/Unraid-API-RE-icon.png failed, reason: self signed certificate 2024-10-05 00:27:46 [error]: request to https://192.168.50.50:448/state/plugins/dynamix.docker.manager/images/CloudflaredTunnel-icon.png failed, reason: self signed certificate 2024-10-05 00:27:46 [error]: request to https://192.168.50.50:448/state/plugins/dynamix.docker.manager/images/code-server-icon.png failed, reason: self signed certificate 2024-10-05 00:27:46 [warn]: Skipping VMs for https://192.168.50.50:448 2024-10-05 00:27:46 [error]: request to https://192.168.50.50:448/state/plugins/dynamix.docker.manager/images/backblaze_personal_backup-icon.png failed, reason: self signed certificate 2024-10-05 00:27:46 [error]: request to https://192.168.50.50:448/state/plugins/dynamix.docker.manager/images/binhex-krusader-icon.png failed, reason: self signed certificate 2024-10-05 00:27:46 [error]: request to https://192.168.50.50:448/state/plugins/dynamix.docker.manager/images/SpeedTest-By-OpenSpeedTest-icon.png failed, reason: self signed certificate 2024-10-05 00:27:47 [warn]: Skipping VMs for https://192.168.50.50:448 2024-10-05 00:28:25 [error]: File config/mqttDisabledDevices.json not found! Creating it with empty array [] Error: ENOENT: no such file or directory, open 'config/mqttDisabledDevices.json' at Object.openSync (node:fs:590:3) at Object.readFileSync (node:fs:458:35) at updateMQTT (/app/mqtt/index.ts:389:21) at Timeout._onTimeout (/app/mqtt/index.ts:441:5) at listOnTimeout (node:internal/timers:559:17) at processTimers (node:internal/timers:502:7) { errno: -2, syscall: 'open', code: 'ENOENT', path: 'config/mqttDisabledDevices.json' } 2024-10-05 00:28:26 [warn]: Skipping VMs for https://192.168.50.50:448 2024-10-05 00:29:26 [warn]: Skipping VMs for https://192.168.50.50:448 2024-10-05 00:30:26 [warn]: Skipping VMs for https://192.168.50.50:448 ``` Thanks!
October 5, 20241 yr Author @StylishQuoter the logs say that it’s because of the self signed certificate. I haven’t tested that functionality. Can you tell me how you set it up? Self signed cert only for an ip. What’s the use case?
October 7, 20241 yr On 10/5/2024 at 12:47 AM, BoKKeR said: @StylishQuoter the logs say that it’s because of the self signed certificate. I haven’t tested that functionality. Can you tell me how you set it up? Self signed cert only for an ip. What’s the use case? Thanks for helping take a look. This is my management access page. And this is my docker compose: container_name: GUS-unraidapi image: bokker/unraidapi-re:6.12 # Use tag for your version - 6.11 or 6.12 network_mode: bridge hostname: ${HOSTNAME} ports: - ${UNRAID_API_UI_PORT}:80 volumes: - ${APPDATA_PATH}/GUS-UnraidAPI:/app/config environment: MQTTBroker: 192.168.[redacted] MQTTPort: 1883 MQTTBaseTopic: homeassistant KeyStorage: config TZ: ${TIMEZONE} restart: unless-stopped depends_on: - influxdb labels: net.unraid.docker.icon: https://raw.githubusercontent.com/ElectricBrainUK/UnraidAPI/master/static/iconx64.png net.unraid.docker.webui: http://[IP]:[PORT:${UNRAID_API_UI_PORT}]/ I'm using the compose plugin setup for it but I also tried the CA app with same configuration. It is the same that only Docker is available. In the app, server address I used "https://192.168.[redacted]:448" with username password. Is it that it can't work with https with self cert? Thanks! Edited October 7, 20241 yr by StylishQuoter
October 23, 20241 yr Author https://discord.gg/GjAyxvuyEx Feel free to join my discord for direct support.
October 27, 20241 yr Hi, it looks like Unraid-APi doesn't seem to pick up multiple cache pools? I have an SATA ssd cache pool (256+512gb) and an NVMe drive (512gb for docker AppData) and it reports only the nvme pool as cache to MQTT. The SATA Cache pool isn't reported to NVMe at all. Is there anything I can do to work around this issue?
November 5, 20241 yr On 9/30/2024 at 9:54 PM, the_lucifer said: Hi, I see an weird error where it simply refuses to find the webui of the tower (I've verified that the URL is correct). I'm not using the default unraid webui port (webui is at a random port: 4123 instead of 80, and I'm reverse proxying the webui to this url): 2024-09-30 23:46:23 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:46:23 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:46:24 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:46:25 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:46:25 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:46:28 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:46:30 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:46:30 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:46:30 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:46:36 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:46:37 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:46:41 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:46:46 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:46:51 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:46:56 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:47:01 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:47:06 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:47:11 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:47:16 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:47:21 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:47:27 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:47:32 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:47:37 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:47:37 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:48:37 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:49:37 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:50:37 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:50:46 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:50:52 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:50:57 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:51:02 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:51:07 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:51:12 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:51:17 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:51:23 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:51:28 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:51:33 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:51:37 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:51:38 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:51:43 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:51:48 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:51:53 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:51:58 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:52:03 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:52:08 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:52:13 [error]: Failed to fetch login for http://web.tower 2024-09-30 23:52:18 [error]: Failed to fetch login for http://web.tower Any ideas on how to fix this? I've attempted everything save setting the webui to 80 @the_lucifer did you ever figure this out, im having the same issues and cant seem to get this to connect to my server
November 11, 20241 yr On 10/2/2024 at 10:41 PM, BoKKeR said: @ABEIDO it’s currently running in dev mode, it’s something I totally forgot about. Today I managed to build the files and rewrite the dockerfile. Yet Somehow the backend did not package properly. Once I figure it out the size will be around 370mb @BoKKeR Any update on when this could be coming out? Edited November 11, 20241 yr by ABEIDO
November 16, 20241 yr Author On 11/11/2024 at 5:01 PM, ABEIDO said: @BoKKeR Any update on when this could be coming out? I have checked on it but since I am using typescript and this is a backend+frontend project it quite difficult to build in a way that both components work In the meanwhile could you remove dangling images, I usually run this command, read in the console what it doas: docker system prune -a WARNING! This will remove: - all stopped containers - all networks not used by at least one container - all images without at least one container associated to them - all build cache Edited November 16, 20241 yr by BoKKeR
November 18, 20241 yr @BoKKeR tnx for maintaining this. Do you know why the statuses of VM's are unknown in HA? It is just a matter of sending this info trough MQTT because on the UI I can see that the API has this information.
November 23, 20241 yr @BoKKeR I tend to run a daily script with docker image prune -af and docker volume prune -f to keep it clean. Only thing that was noted on system prune: Deleted Networks: br0 Edited November 23, 20241 yr by ABEIDO
February 4, 20251 yr I wanted to note that there seems to be a caching issue. I could reproduce the issue with the following steps: 1. Start a parity check 2. Get "parityCheckRunning" boolean via API json = requests.get("http://192.168.178.26:3005/api/getServers", timeout=3).json() print(json['servers']['192.168.178.26']['serverDetails']['parityCheckRunning']) It returns "False" (Wrong!) 3. Run the same Code again to get the "parityCheckRunning" boolean The second API request (And the following ones) returns "True".
March 3, 20251 yr After recent Unraid updates the vm sensor is having problems buy not getting updated after HA restart. Also issues with a large Unraid API container still present as its still seems that the container is running in dev mode as the container is over 1 gb. Is there any ongoing work on Unraid API-RE?
September 2, 2025Sep 2 Since Unraid 7.2 will have a built-in official API there would be no point for this "hackish" way of doing things anymore.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.