I can connect locally to hub on LAN but not remotely. The remote access was working ok previously but I have not used it in a while.
Hub C8
Version 2.3.6.146
Using the Hubitat App: it asks me to select a hub. I can see the hub listed but get an error "java.io.IOEXCEPTION: Failed to get DashboardData, hubitat API:the..."
Using the Remote Management App: Under "registered hubs", I can see the hub and select hub details and it shows that the hub is active and last checked in at the current time. When I select "connect to hub" it opens a page with a "remoteaccess.asw.hubitat.cxx" address and then just sits there and times out with a message "this page isn't working".
I have tried:
Soft power reboot
Hard power reboot
Router and modem reboot
The IP address should not have changed recently. It is DHCP with a local reservation and I have been using shortcuts to the IP for years. I did try the network reset button previously, but I couldn't tell if it did anything.
I tried the following link and the page responds "operational" with a green check:
Hmmmm. I dont recall deleting any dashboards but after reading your comment i did notice there is a direct link option to each dashboard in the new firmware. I tried connecting to a current dashboard via the direct link and i get a message "No response from hub"
Can you ping an FQDN instead of an IP address? If the former fails (and we already know that the latter works), then issue could be that your hub doesn't have access to a DNS.
This matches the symptom of the platform not working to download the update, but the diagnostic tool working. They are separate processes that get their DNS configuration differently.
Unable to ping FQDN. I manually added DNS servers (same as on router) and selected override DNS settings and can ping FQDN now.
Still no cloud connection. What I don't understand is that when I go to the hub details on my phone (not on LAN), it shows that the hub is active and last check-in is the reboot time from a couple minutes prior. Seems like something is talking.
Have you tried deleting the app from your phone and then re-downloading the app? Sometime the app maintains setting and the re-loaded app will use the setting from the old app.
Deleting the app will remove all settings giving the freshly downloaded app the opportunity to setup itself up properly.
Hello. Yes, I have removed the apps and reinstalled from the phone. Unfortunately, same issue. I also have a laptop on a different (starlink) network and it also is unable to remote admin. But it too can connect just fine when on the local LAN.
You are having problems connecting from your phone to the hub for remote admin. Can you connect to your remote dashboards? If you can it would suggest your networking is working properly and you have a subscription problem. Are you able to send notifications from the Hub to the phone (opposite direction)
Try accessing your cloud dashboards from the Hubitat website. By performing this test directly from the website you've also eliminated any issues with the phone app.
i dont even have the "dashboard menu links: cloud dash board menu" option. the page shows a last check-in with a date time form earlier today, then it shows my remote admin subscription then advanced options directly beneath that.
I probably should have first confirmed that you actually have created some cloud dashboards to be able to do this test.
Since you were able to update the hub's firmware, I don't think you have a networking issue. I think you may have a subscription issue.
If that theory is correct, then you should be able to access your cloud dashboards.
You may also want to send a notification to your phone from the hub to confirm that is working or not working, because that does not require a subscription.
Can you confirm that the IP address shown on the hub information page matches your hub's IP address?
If there's no cloud connection, remote admin will not work. It relies on the cloud connection to start the remote session. The hub is using AWS IoT connection. If there's anything on the network that stop that, it's the culprit.
Do you have the v2 app with the green background icon?
I would try remote admin from portal.hubitat.com to eliminate the app as a possible issue. You log in there and go to registered hubs. Sounds like maybe you tried this already? I would not focus on the mobile app until that is working. Try it from a mobile device with Wi-Fi shut off to be sure it works remote.
For DNS you should not need to override it, it should be able to get it from DHCP. There is a DNS setting to also include extra DNS servers, you may need to turn that off if you want to be sure you use a specific one.
What is your DNS setup? Do you a blocker setup like pihole or AdGuard home? Do you have anything on your router that blocks dns connections outside the lan? (For example to prevent a device from using google 8.8.8.8 for dns)
yes, ips match. I also tried sending two test notifications to my phone (remote connection) via a basic rule created and a notification from the phone/mobile device app listing in the devices list on the hub using a LAN connected laptop. neither of the notifications were received on my phone.
I dont think there is anything blocking aws connections on my lan.
i do have the app with the green background. I recently deleted and reloaded incase it was a app issue. i dont have any dns blockers
yes. i have a laptop with a separate starlink to connection to test remote access while not on the LAN. no luck with remote assess there either. But here is an odd new thing: previously when i tried this, the aws would just time out and never connect. today i am actually reaching the remote admin page and it shows my hub name with options to connect, reboot and update software. when i select connect, it times out. when i send a reboot request, the hub does not reboot
