c-7 everything set up a year ago and been working well, now want to make some changes and realized I cannot access my hub to do anything. Everything still working, can use my dashboard on my phone just fine but login to my.hubitat.com and "Connect to Hub" button says "This site can’t be reached ... took too long to respond". So I thought I would be clever and sign up for this remote access and sadly "Go to Remote Admin" gets me "This page isn’t working remoteaccess.aws.hubitat.com didn’t send any data. ERR_EMPTY_RESPONSE" (might have to cancel that before I have to pay for something that gained me nothing). Not sure what to do at this point so here I am for the first time.
Facts: I did switch router to a Xfinity xFi Gateway (white) away from a personal router since last remote access (can see hubitat as a device in xfinity home app). From Hubitat App can tell hub is on Version 1.6.1 (which needs to be updated for devices in app)
I would try restarting your hub to see if that helps. My guess is that maybe your new router is assigning IP addresses in a different range from your old one, and Hubitat might still think it's in the "old" range. If your router has a way to see currently connected devices and their IP addresses (most do), you could first try to access it that way to see if you can find anything. The website you linked to should also work if the hub has cloud connectivity, or you can just go to find.hubitat.com directly to scan your network or see what I assume is its last cloud-reported addresses.
If you think you know its IP address but the regular interface isn't working, consider trying port 8080 instead, i.e., http://yourHubIP:8080 to see if that helps (alternate port for the same interface), then try Settings > Reboot Hub. If not, try port 8081, which is the diagnostic tool and should also have a reboot option. If nothing else, you might have to do what is otherwise a no-no: unplug the hub for a few seconds and plug it back in to restart.
Ultimately, the hub's admin interface is just a webpage, and it's easier to consistently get to if you assign a "static" or DCHP reserved address in your router. That's not technically a requirement, but it eliminates the need to either use the app or the "find" utility to get to your hub if its IP address changes--so just something you might want to consider for the future. But hopefully you can get this problem figured out first!
Happy to help! Someone who knows more about networking could explain it better than I…
As I understand it, the hub registers itself as « Hubitat » on the local network, so using the link above will connect to the hub. If I click on it, I get connected to my local hub.
Hi!
I just have the same problem, the button (connect to hub) on the web or inside the app is pointing to a wrong ip adress... How can I correct this? Because in web browser I can use the http://hubitat.local but inside the app the button connect to hub is not even there anymore... pretty weird... could it be something in relation with dynamic ip adress in the router?
Thanks
If I remember correctly, a reboot might help resolve this, or waiting for a bit until the new IP is sent out. Best thing to do is setup a reserved IP address on the DHCP server.
