I cannot get the hub's web interface to load. I can load the diagnostics menu (port 8081), but I cannot get the normal web interface to load. I can see the hub connected to my router through my router's interface. The portal (portal.hubitat.com) can find the hub, but when I click on it, the interface will not load. I recently updated my firmware on my router (Netgear Orbi) to the newest release, but I do not think that is affecting it. Any help would be appreciated.
Have you tried a different browser?
Updated my Orbi RBR40 to firmware V2.6.1.36 about 10 days ago. Hub would not connect on any port after a router reboot. Had to do a hub power cycle to reconnect. Since you can get to the diagnostics menu, suggest trying a "Reboot Hub".
1 Like
Anytime I update my router firmware I've just gotten in the habit of restarting any device that's semi-intelligent (hubs, smart TVs, connected sound systems, etc.) Just saves me time and aggravation downstream.
1 Like
I have not. I can try IE when I get back home. However, the Hub light stays blue and I can access port 8081. When I try to do a restart, I get a 401 error.
I restarted it a few times and I am still getting the same result.
I also enabledDisney Circle, but it is in the unmanaged devices group.
What version hub is this? That means different things depending on the version of hub.
It is the one with built in zigbee and zwave.
This normally means that your log in to the diagnostics page has timed out.
Hit logout and then log back in again.
Hopefully this will get you access to the diagnostics again.
Well, that worked. Unfortunately, I lost all my apps and devices. I knew I would lose apps, but I thought it said my devices would remain. Oh well. Saved me $129.95 though. Thank you!
Did you do a soft reset?
Did you do a backup?
There may be one one available on the hub.
I did a soft reset. I found a backup from 11/7. That may work for me. I will try that. Will I still need to reconnect all my devices with the backup?
You shouldn't have to.
They should work once the backup is loaded.
Some people have advised to do a reboot after the backup has been loaded and things have settled down just to make sure everything is OK.
It has been a while since I did one so cannot be certain.
Looks like it is back up and running. Thank you very much for your help!
Welp. Looks like it died again.
Probably not the issue, but make sure the hub isn't sitting on top of something warm/hot. In my experience my hubs will lock up sitting on top of a barely warm network switch, but won't when on the desktop.
Ignore my last message. I had switched the power supply on the hub, thinking maybe it had gone bad. I used my power supply for my raspberry Pi that is running the WyzeNet integration. When the hub booted up, my Webcore Piston noticed the Pi was down, so it switched off the power to the Pi to restart it. I switched the power supplies back and it seems to be working now. Thanks everyone!
4 Likes
Just for info. Every time I do any changes I do a backup and save it to my PC.
If things do go pear shaped (I know there should be the latest backup on the hub) I have got my latest hub build available.
You may already do this but thought I would mention it.
Glad you got things going again. 
1 Like
This has happened to me a lot after updating my C7 to 148. I'm very anxious for new firmware to be released. I'm hoping this fixes the issue. In my case a hard power cycle fixes the problem. It's pretty sad that I need to setup a Wi-Fi outlet to allow me to power cycle my Hubitat. 
It works for now. I'm not 100% sold that your issue is the router. It's not in my case. FWIW, reset & shutdown do not work for me in diag mode when I am stuck in the mode. My only option is to power cycle the Hubitat.
