It gets stuck like This ...! After pressning Go to remote admin bild|230x500
It's up and running now, and I'll be taking a closer look at it. Current version has gone through beta, but the load is higher now, and it may need some tweaking in the next day or two.
1 Like
It just hangs for me:
The full URL it's hanging on is:
https://remoteaccess.aws.hubitat.com/proxy/remoteConnectWithTokenPostI'm taking a closer look at it today - things worked fine in beta but there apparently are issues as more people start using it. It's been restarted and is accessible again in the meantime.
I also can't access.
And in the Android app when I click on Connect to Hub, even when on local network, the app just closes.
1 Like
Mines working great now.
Hi It still doesn't work..... Any solution cumin up?
Mine is sort of hit-or-miss. Right now it's working fine.
Mine just hangs there too...
But it's now working great, a couple hours later.
That's the way mine is.
Have you guys created tickets with support?
Regardless, @gopher.ny appears to be working on getting this new feature working optimally now that its been released from beta testing.
But since they have an email ticket system, it would probably help them even further for tracking purposes if people also logged their issues that way?
Yeah, it's at the very top of my list - tag me if you experience issues connecting.
I've done a couple of updates yesterday, and force disconnected a few people in the process, but in general I try to wait for a lull in activity before rolling anything out.
3 Likes
I'm just wondering if the system might be a little overloaded with a lot of people checking it out since it's new. I'm gonna wait it out for a few days and see what happens.
When I try it and it doesn't work, I can wait a few minutes, try again, and then it works.
Since there is no hub exposure to the wider internet, remote admin has to tell the hub to dial in. It sounds a bit like putting cart before the horse, but it is a far more secure approach. Anyway, those pings that tell hub to connect are not guaranteed delivery. I'm fine tuning things based on feedback and live logs, so the service will improve over the next few days. And yes, remote admin went through a beta cycle, but of course many more people use it now.
As far as capacity goes, there's plenty to go around. Clicking Go to Remote Admin button multiple times is not going to overload anything 
1 Like
It's working fine for me. Would be really nice to have it integrated with the IOS (and Android) mobile apps...
2 Likes
It wasn’t working for me yesterday or earlier today but is working now.
@gopher.ny: I just signed up for the remote access...and am not able to connect. It's just sitting at this URL:
https://remoteaccess.aws.hubitat.com/proxy/remoteConnectWithTokenPost
and them times out..."ERR_EMPTY_RESPONSE"
If it helps, I signed up from work (over my lunch break) at the office, and not from the local network the hub is on.
Thinking it might be a firewall issue at work, I connected my iPad to my phone via personal hotspot...same issue.
I'm getting the same thing from my home. I have 3 hubs in 2 locations. So far I have been able to connect to only one hub, two times over multiple attempts. Two of the three hubs I have not been able to connect remotely at all. Keep thinking perhaps this is load related for new users coming on, but if it doesn't settle down and get some consistency soon I'll opt out before the 'free' time period lapses and go another route.
Do you have hub UI security on by any chance? I fixed a related issue in 2.2.6.133, which is out as of a few minutes ago. Please let me know if that works, I'll take a closer look if it doesn't.
I don't have UI security enabled and I have had mixed results. Sometimes it works fine, but this morning I couldn't connect the first half-dozen tries. I'm using the mobile app. It doesn't error out (but might have eventually)... but it just never connects. And then it does. Almost as if it was a load balancer VIP configuration issue, or one of several nodes behind the LB is flaky.
1 Like
