Trying to recover from Error 500

🛎️ Get Help
1

I have a C-8 hub. I believe I'm running .164 but I can't get into the web UI right now to check.

Things over the past few days have been flakey. Sometimes control of devices would work, other times not so much. Finally, tonight control of devices just wasn't happening. I logged into the hub and the web UI was very slow. Going from one menu item to another could take up to 10 seconds. When I tried to look at the details for a device I just got error 500. So, I did some reading of posts, went to the diagnostic tool, downloaded a few backups, and did a soft reset.

My hub then rebooted and It has been at least a half hour trying to work its way through starting up. I thought it was stuck at 25% but it has moved up to 60% and has been stuck here for at least the last 10 minutes. Given this, I'm not confident that the soft reset has helped.

I'm going to leave the hub trying to start up overnight as it is now midnight

Ideas would be welcome. Thanks in advance for the help

2

Top o’ the morning. Was wondering about the current status of your issue.

3

After 6+ hours the startup is still stuck at "Initializing Hub: 60% - Starting UPNP"
:cry:

4

Can you still get to port 8081?

5

I power cycled the C-8. When I connect to the IP address of the hub I get nothing. No startup messages, etc. However, I can still connect to 8081.
Thanks

6

Re do the soft reset from port 8081. Also what version of the tool do you have at the moment? Current is 1.1.130

7

Update. I just received the following on the c-8's IP address:
"Hub cannot continue. To fix a corrupt database, the hub needs a soft reset"
I'll try a second soft reset.
Thanks

1 Like
8

If that doesn't fix it, do a platform roll back

9

Thanks.

10

Do you have a hub protect subscription?

11

No I don't. I just tried reverting to .157. Waiting for hub to reboot.

12

The hub seems to be stuck in a spinning "Hub is rebooting, Please wait..." with the diagnostic tool. However, I have to run out with my wife for a few hours so I'm going to cross my fingers and hope that it takes a while to revert to a different firmware version. So, I'll see what happens when we get back. :crossed_fingers:

13

The diagnostic tool is still spinning but my link to the main hub UI just came back with another corrupted db message. I'll try another soft reset

14

Some progress. I ended up enabling safe mode and doing another soft reset. That allowed me to boot. I then restored a backup from a month ago before I started trying to integrate an Aqara Matter compatible smart lock using the Advanced Matter Bridge Software. That restored my devices, etc. and I then updated to firmware .166.

Now everything looks fine in the UI (all my devices seem to be there, all my apps are there, etc.) and I can control them through the Hubitat UI.

What does seem to not be working is my integration through the Maker API but that I can work on debugging.

Thanks for all the help. I never thought I would need to use the diagnostic tool but I feel like an expert now :rofl:

1 Like
15

Check your ip..

16

Thanks for the suggestion. I have it all working now. FYI I have my C-8 on a DHCP reservation to avoid the issue you referenced. Thanks again for your help

1 Like