[Support] Electric Brain Unraid API


Recommended Posts

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.

Link to comment
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).

Link to comment
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)

Link to comment
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?

Link to comment
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...?

image.png.01082a90b46195135384a01e94a7181e.png

 

This is what the UI shows, and occasionally I get extra details, all that say false

Link to comment
7 minutes ago, Flendor said:

Would it then not connect at all...?

image.png.01082a90b46195135384a01e94a7181e.png

 

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

Link to comment

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

Link to comment
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?

Link to comment
  • 2 weeks later...
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.

 

Link to comment
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

  • Like 1
Link to comment

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?

 

image.png.b438f6ee62d0771ea1c3d2266f58c119.png

Link to comment
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?

 

image.png.b438f6ee62d0771ea1c3d2266f58c119.png

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!

Link to comment
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!

  • Like 1
Link to comment

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

Link to comment
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

Link to comment
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

> unraidapi@0.5.0 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

 

Link to comment
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 🙂

Link to comment
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!

Link to comment
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

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.