Webcore does not start on C8

I updated my C7 to 2.3.5.105. I did that too on my C8. I then restored on my C8. Now, the app Webcore on Hubitat does not start (please wait loading app). I even used HPM to repair it, same thing. Any idea ? Should I remove it and reinstall it if no other option ?

1 Like

Some people have had success by manually re-entering the DNS settings - Settings|Network Setup|Override DNS Settings , enter * 8.8.8.8, 8.8.4.4, 1.1.1.1, 1.0.0.1, 9.9.9.9*, and click Override

1 Like

I ran into the WebCoRE startup problem too. I was unable to bring up the app in the IDE. It would just sit there saying "loading app" My issue was caused by Maker API. I had not re-linked my devices. Once I did that WebCoRE came up with no issue. I have converted one of two hubs and so far the first migration went well, other than the few minutes it took to re-link about a dozen devices.

You will have to logout from your WebCoRE dashboard and use "Register a Browser" to get things going again.

After overriding the DNS I can access Webcore app. But after registering my Browser I don't have access to the pistons the message is the data shown is outdated...

I'd like to try to remove the DNS but it does not accept BLANK

NOTE: Now it works, I had to close my VPN to register the browser.

What you mean RELINK the devices in Maker API ? I clicked on DONE in the maker API and in Webcore but I cannot access the pistons, the message as I said previously is the data shown is outdated.

NOTE: Now it works, I had to close my VPN to register the browser.

when I displayed my devices there were several of them showing up OFFLINE and disabled. Those devices were also used in webCoRE. I went into each OFFLINE device and in the Device Information section I used the "Keep current device link" drop down and changed it so it matched to the device on the migrated hub. Once I got all my devices back online launching the webCoRE app using the IDE allowed it to load. I was then able to select "Register a browser" so I could get my dashboard back up and running.

After reading dnickel's reply below, what I thought was a Maker API problem may have been a coincidence in that during the time I was re-linking could have been enough time for dnickel's idea of webCoRE's recompiling to complete. I too had a severer hub load message that since cleared up.

Intestingly enough, I had the same issues and tried all the various fixes.
I noticed that my CPU remained at 50% with a warning.
I waited it out and finally gave up and rebooted.
WC started working by itself and from what it appeared, WC was recompiling that whole time; once done I could log in.
Just my guess.

1 Like

That make sense ! I waited 30 minutes but maybe it was not enough...

@thebearmay I'd like to test without it, any idea how to remove the DNS override ?

All we did was set the DNS back to the defaults, but as long as you enter a valid IP address it will save it.

And what was the default ? It's impossible to clear the field

8.8.8.8, 8.8.4.4, 1.1.1.1, 1.0.0.1, 9.9.9.9

OK, i entered that value but I thought it was an empty field before.

That’s the default but normally it’s in the background.

1 Like

I talked to support and they will change it so we can clear that field.

Btw, this fixed my webcore problem but ALSO my zigbee network that was BOOTING forever. Now everything is fine. Thank you @thebearmay

1 Like

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.