Hub locked, and yet it **is** accessible

🛎️ Get Help
1

Hi

My hub is locked again... Didn't really do anything. Was functional when I left work, and when I arrived home it was in "locked mode"...

So I cannot access my hub on the normal IP of 192.168.0.8. I get

image

AND YET IS FULLY ACCESSIBLE!!!!!!!! On port 8081:
AND YET IS FULLY ACCESSIBLE!!!!!!!! On port 8081:

image

Is there any way to force a reboot without pulling the plug? Not going to be home for a few days...

The command http://192.168.0.8:8080/hub/reboot (if memory serves me correct) has been deprecated, and if not (I'm on V1.1.7.120), it is giving me a "connection refused" error as well. So why is the hub fully accessible on port 8081??

Thanks in advance
J

2

Very interesting data, thanks for it.

I think the command is http:// << ip address >> /hub/reboot

Edit, i see you tried with that too.

Then a wifi plug would be your savior

3

They are both correct:
http://192.168.0.8:8080/hub/reboot
http://192.168.0.8/hub/reboot

Neither function though...

J

4

Yes, 1st thing I am doing when I get back.

5

Any third party apps running?

6

Yes, lots, but lets ignore that for the time being...
There was no tinkering with the system today.

Why would a hub be inaccessible on port 80 & yet accessible on port 8081?

If any app is causing it to lock up, it is either locked or not. Not partially accessible on another port.

J

7

I just tried with my developer hub and I get a 404 error from the OS, so yes, your hub is locked on port 80

8

Not a hard question at all. I have several potential answers.. but the easiest to type is: it's a 4 core processor, one core is reserved for running... yep. 8081

9

8081 is almost always accessible even with the hub is locked up. And unfortunately, it sounds like you’re going to have to pull the plug, wait 30 seconds, plug it back in

10

So a 404 error is a "page doesn't exist" error.
Not what I am getting; I'm getting connection refused.

J

11

Yes.

Screenshot_20181128-221337_Chrome
Screenshot_20181128-221337_Chrome.jpg1079×976 142 KB

12

Yes I am coming to that conclusion as well.

I think that @mike.maxwell, @bravenel, @bobbyD, @patrick should note this & implement a reboot functionality that is accessible on port 8081 as well in a future upgrade.

J

13

The hub runs a separate process for port 8081. This is independent of the main hub software. Which runs on port 80. Something has caused the main hub software to crash and it needs to be restarted.

/Hub/reboot has been moved to a post request so it isn't directly accessible but it is still there.

A reboot if the hub is the next step.

14

Again, I am NOT getting a 404 error.

15

Ehh, probably that will come when they secure the 8081 entry. Or maybe another port for that.

16

I know, that's why I said yes, you have your hub locked

17

Can support reboot it?

18

I think Patrick has already clearly stated in another thread they will NOT secure 8081.
Making a reboot function accessible on that port is, in my opinion, not a security risk at all.

J

19

Good question!!!!! Can support reboot it remotely upon request in the absence of myself being able to do it in a timely manner?

20

No this is not a function of support. Apple doesn't reboot your phone if it crashes. Microsoft doesn't reboot your server if it crashes.

Hubitat can not reboot your hub if it crashes.