ElectricBrainUK Posted March 22, 2021 Author Share Posted March 22, 2021 Just now, Flendor said: Thank you in advance for any support that you can give. I have installed the Unraid_API docker with the default configuration. The log file is spamming "Get main details for IP address x.x.x.x failed" "request failed with status code 503" The Unraid_API webgui shows connected, and displays the IP address of the server and the title, but nothing else. Hi, For the username did you use the root account? Others don't work at the moment. Quote Link to comment
Flendor Posted March 22, 2021 Share Posted March 22, 2021 Just now, ElectricBrainUK said: Hi, For the username did you use the root account? Others don't work at the moment. Thanks for such a quick response. Yes i did Quote Link to comment
ElectricBrainUK Posted March 22, 2021 Author Share Posted March 22, 2021 1 minute ago, Flendor said: Thanks for such a quick response. Yes i did Okay interesting, can you access the unraid ui normally? 503 suggests it's struggling to connect to unraid so it could be a username password thing, it could also happen if the unraid ui was down, or it could happen if you have the api on a bridge with its own ip address and you're trying to connect to the host (unraid network setup doesn't let you do this). Quote Link to comment
Flendor Posted March 22, 2021 Share Posted March 22, 2021 2 minutes ago, ElectricBrainUK said: Okay interesting, can you access the unraid ui normally? 503 suggests it's struggling to connect to unraid so it could be a username password thing, it could also happen if the unraid ui was down, or it could happen if you have the api on a bridge with its own ip address and you're trying to connect to the host (unraid network setup doesn't let you do this). Yes, I can connect to the main Unraid UI, and all other Dockers. The main server (eth0) is on a static IP address with all dockers (except Plex) either Bridge or Host. A seperate interface card (eth1) is used for Plex docker (br1) Quote Link to comment
ElectricBrainUK Posted March 22, 2021 Author Share Posted March 22, 2021 3 minutes ago, Flendor said: Yes, I can connect to the main Unraid UI, and all other Dockers. The main server (eth0) is on a static IP address with all dockers (except Plex) either Bridge or Host. A seperate interface card (eth1) is used for Plex docker (br1) That is weird, sounds like all should be fine then. Is there a chance the password entered was wrong? Quote Link to comment
Flendor Posted March 22, 2021 Share Posted March 22, 2021 2 minutes ago, ElectricBrainUK said: That is weird, sounds like all should be fine then. Is there a chance the password entered was wrong? Would it then not connect at all...? This is what the UI shows, and occasionally I get extra details, all that say false Quote Link to comment
Flendor Posted March 22, 2021 Share Posted March 22, 2021 7 minutes ago, Flendor said: Would it then not connect at all...? This is what the UI shows, and occasionally I get extra details, all that say false Okay, I have reset the root password and things seem to be happening. Wierd as I set changed the password to what it was in the first place. Thanks anyway Quote Link to comment
ElectricBrainUK Posted March 22, 2021 Author Share Posted March 22, 2021 1 minute ago, Flendor said: Okay, I have reset the root password and things seem to be happening. Wierd as I set changed the password to what it was in the first place. Thanks anyway Glad that it is working now - let me know if you need anything else Quote Link to comment
Orbsa Posted March 25, 2021 Share Posted March 25, 2021 I have attempted setting up the Unraid-API as a docker on a bridge network 10.0.0.0/24. After multiple attempts to login with the right address for unraid, root user and password, the program fails to connect to the server. Logs show the following connect EHOSTUNREACH 10.0.0.10:80 Get Dashboard Details for ip: 10.0.0.10 Failed with status code: undefined connect EHOSTUNREACH 10.0.0.10:80 Get VM Details for ip: 10.0.0.10 Failed connect EHOSTUNREACH 10.0.0.10:80 Get Docker Details for ip: 10.0.0.10 Failed When adding it says it says Logged in successful, Shows up as 'Server' on the right before disappearing (presumably from lack of a found hostname). an API call shows it as offline. I can login to the server at http://10.0.0.10 on the bridge network using the user/pass. I have done so from a VM without issue. I am running unraid 6.9.1 Quote Link to comment
ElectricBrainUK Posted March 25, 2021 Author Share Posted March 25, 2021 4 hours ago, Orbsa said: I have attempted setting up the Unraid-API as a docker on a bridge network 10.0.0.0/24. After multiple attempts to login with the right address for unraid, root user and password, the program fails to connect to the server. Logs show the following connect EHOSTUNREACH 10.0.0.10:80 Get Dashboard Details for ip: 10.0.0.10 Failed with status code: undefined connect EHOSTUNREACH 10.0.0.10:80 Get VM Details for ip: 10.0.0.10 Failed connect EHOSTUNREACH 10.0.0.10:80 Get Docker Details for ip: 10.0.0.10 Failed When adding it says it says Logged in successful, Shows up as 'Server' on the right before disappearing (presumably from lack of a found hostname). an API call shows it as offline. I can login to the server at http://10.0.0.10 on the bridge network using the user/pass. I have done so from a VM without issue. I am running unraid 6.9.1 Ah right, weird that it can't connect. Are you sure that you can connect to the unraid host? Doing a test from a VM doesn't necessarily mean it will work as it is to do with how the docker engine handles the custom network: I would test using the console in a docker just to be sure if that's okay? Quote Link to comment
Orbsa Posted March 25, 2021 Share Posted March 25, 2021 You are right. Default docker settings in unraid were set to not allow host contact. I've fixed that and it is working as expected. Thank you very much. 2 Quote Link to comment
Drazzilb Posted April 2, 2021 Share Posted April 2, 2021 WARN mode option is deprecated. You can safely remove it from nuxt.config READY Server listening on http://0.0.0.0:80 Failed to retrieve config file, creating new. ERROR ENOENT: no such file or directory, open 'config/mqttKeys' at Object.openSync (node:fs:492:3) at Proxy.readFileSync (node:fs:393: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 (node:events:378:20) at SendStream.EventEmitter.emit (node:domain:470:12) Get Main Details for ip: 192.168.1.200 Failed Request failed with status code 503 Get Dashboard Details for ip: 192.168.1.200 Failed with status code: [object Object] I too seem to be having issues with getting this container to work. Running latest Unraid version: 6.9.1 Docker version: 19.03.14 Install variables are all default from the template. When adding a server I'm using the host's IP address Root as username and my password. Which also I've reset as mentioned by Flendor earlier. With no luck. Running multiple containers w/a single VM. Quote Link to comment
Drazzilb Posted April 2, 2021 Share Posted April 2, 2021 1 hour ago, Drazzilb said: WARN mode option is deprecated. You can safely remove it from nuxt.config READY Server listening on http://0.0.0.0:80 Failed to retrieve config file, creating new. ERROR ENOENT: no such file or directory, open 'config/mqttKeys' at Object.openSync (node:fs:492:3) at Proxy.readFileSync (node:fs:393: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 (node:events:378:20) at SendStream.EventEmitter.emit (node:domain:470:12) Get Main Details for ip: 192.168.1.200 Failed Request failed with status code 503 Get Dashboard Details for ip: 192.168.1.200 Failed with status code: [object Object] I too seem to be having issues with getting this container to work. Running latest Unraid version: 6.9.1 Docker version: 19.03.14 Install variables are all default from the template. When adding a server I'm using the host's IP address Root as username and my password. Which also I've reset as mentioned by Flendor earlier. With no luck. Running multiple containers w/a single VM. Figured it out. Instead of using the host IP I used the hashed one... Thanks 1 Quote Link to comment
MostHated Posted April 6, 2021 Share Posted April 6, 2021 Hey there, I am having an issue where the Home Assistant plugin is not loading or saving the config on a fresh install. https://github.com/ElectricBrainUK/UnraidAPI/issues/32 Quote Link to comment
makkish Posted April 9, 2021 Share Posted April 9, 2021 Hello, First of all, thanks for a great plugin that opens many doors. One question, I can see in the pihole logs that as soon as I start the container it starts querying hassio every second. Why is that? Quote Link to comment
ElectricBrainUK Posted April 10, 2021 Author Share Posted April 10, 2021 9 hours ago, makkish said: Hello, First of all, thanks for a great plugin that opens many doors. One question, I can see in the pihole logs that as soon as I start the container it starts querying hassio every second. Why is that? Hey, thanks for letting me know It's strange, it could be a couple of things, do you have the mqtt broker configured? The default broker is hassio Otherwise if you have entered hassio as an ip in the ui it might do that The third option is it's a bug but I think I would've noticed myself as I also use pihole, let me double check that though! Quote Link to comment
makkish Posted April 10, 2021 Share Posted April 10, 2021 1 hour ago, ElectricBrainUK said: Hey, thanks for letting me know It's strange, it could be a couple of things, do you have the mqtt broker configured? The default broker is hassio Otherwise if you have entered hassio as an ip in the ui it might do that The third option is it's a bug but I think I would've noticed myself as I also use pihole, let me double check that though! Hi, Well, now I feel a bit stupid. Of course I had it in the configuration, I did not think of what it meant when I installed it the first time. I removed everything with MQTT/HomeAssistant and the queries stopped. Thank you! 1 Quote Link to comment
ElectricBrainUK Posted April 10, 2021 Author Share Posted April 10, 2021 Ah good news! Quote Link to comment
Thomaslo Posted April 10, 2021 Share Posted April 10, 2021 Same 503 errors for me: Cannot read property 'forEach' of undefined Get Main Details for ip: 192.168.40.100 Failed Request failed with status code 503 Get Dashboard Details for ip: 192.168.40.100 Failed with status code: [object Object] Request failed with status code 503 Get Docker Details for ip: 192.168.40.100 Failed Request failed with status code 503 Get VM Details for ip: 192.168.40.100 Failed Request failed with status code 503 Get Main Details for ip: 192.168.40.100 Failed Request failed with status code 503 Get VM Details for ip: 192.168.40.100 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.40.100 Failed Request failed with status code 503 Get Dashboard Details for ip: 192.168.40.100 Failed with status code: [object Object] Request failed with status code 503 Get Main Details for ip: 192.168.40.100 Failed Request failed with status code 503 Running v6.9.2 Quote Link to comment
ElectricBrainUK Posted April 10, 2021 Author Share Posted April 10, 2021 2 hours ago, Thomaslo said: Same 503 errors for me: Cannot read property 'forEach' of undefined Get Main Details for ip: 192.168.40.100 Failed Request failed with status code 503 Get Dashboard Details for ip: 192.168.40.100 Failed with status code: [object Object] Request failed with status code 503 Get Docker Details for ip: 192.168.40.100 Failed Request failed with status code 503 Get VM Details for ip: 192.168.40.100 Failed Request failed with status code 503 Get Main Details for ip: 192.168.40.100 Failed Request failed with status code 503 Get VM Details for ip: 192.168.40.100 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.40.100 Failed Request failed with status code 503 Get Dashboard Details for ip: 192.168.40.100 Failed with status code: [object Object] Request failed with status code 503 Get Main Details for ip: 192.168.40.100 Failed Request failed with status code 503 Running v6.9.2 503 errors suggests that your unraid api can't connect to your unraid host, how is the networking set up? If you're using a custom bridge the docker network can't communicate with the host. Can you access your unraid ui yourself via a web browser? It is also is possible your username configured is not root, or the password you entered was wrong Quote Link to comment
iamnypz Posted April 12, 2021 Share Posted April 12, 2021 On 4/11/2021 at 1:52 AM, ElectricBrainUK said: 503 errors suggests that your unraid api can't connect to your unraid host, how is the networking set up? If you're using a custom bridge the docker network can't communicate with the host. Can you access your unraid ui yourself via a web browser? It is also is possible your username configured is not root, or the password you entered was wrong Hi, I just upgraded to 6.9.2 and I get theese errors as well. Haven't changed anything regarding network. Log as follows: Spoiler pm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2021-04-11T11_54_59_342Z-debug.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 READY Server listening on http://0.0.0.0:80 Get VM Details for ip: 10.220.0.3 Failed Request failed with status code 503 Get Dashboard Details for ip: 10.220.0.3 Failed with status code: [object Object] Request failed with status code 503 Get Docker Details for ip: 10.220.0.3 Failed Request failed with status code 503 Get Dashboard Details for ip: 10.220.0.3 Failed with status code: [object Object] Request failed with status code 503 Get VM Details for ip: 10.220.0.3 Failed Quote Link to comment
Thomaslo Posted April 12, 2021 Share Posted April 12, 2021 On 4/11/2021 at 1:52 AM, ElectricBrainUK said: 503 errors suggests that your unraid api can't connect to your unraid host, how is the networking set up? If you're using a custom bridge the docker network can't communicate with the host. Can you access your unraid ui yourself via a web browser? It is also is possible your username configured is not root, or the password you entered was wrong I dont know exactly what i did. changed password and back to what i had. Working now 🙂 Quote Link to comment
Thomaslo Posted April 12, 2021 Share Posted April 12, 2021 Is it possible to include cpuload and temperature of the server in the API ? Quote Link to comment
ElectricBrainUK Posted April 12, 2021 Author Share Posted April 12, 2021 1 minute ago, Thomaslo said: I dont know exactly what i did. changed password and back to what i had. Working now 🙂 That is unusual you shouldn't have to do that, glad it's working now and thanks for letting me know. I'll see if something weird happens with the cookies when you upgrade and try to do it automatically for new users For cpu load and temperature I would recommend glances as it has all this information already and I didn't want to repeat someone else's work! Quote Link to comment
Thomaslo Posted April 12, 2021 Share Posted April 12, 2021 55 minutes ago, ElectricBrainUK said: That is unusual you shouldn't have to do that, glad it's working now and thanks for letting me know. I'll see if something weird happens with the cookies when you upgrade and try to do it automatically for new users For cpu load and temperature I would recommend glances as it has all this information already and I didn't want to repeat someone else's work! Thank you. I try glances Quote Link to comment
Recommended Posts
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.