Hi Guys, @bertabcd1234,,
The docs2.hubitat.com seems to be down again as i am getting the same "site cant be reached" error as i was getting the other night.
Any ideas, Thanks
Depending on the browser you use, make sure is not forcing the address to https instead of http. Https is not avaialble yet.
Alternatively, you could try private or incognito mode on your browser (or clear your history) to see if that resolves the problem.
I'm also migrating to Hubitat today and can't reach the documentation so it's not just you having issues. I'm using an MS Edge browser.
I have no issue loading the docs using edge on Android 11.
@bobbyD normally when that is the issue I get a warning about the site not being private. This error is a network error essentially timing out.
The other night the site had to be โresetโ somehow and it came back online. But it is back to unavailable.
I will try the IP address when I get home.
Just adding a data pointโฆ. Working fine here on the East Coast using Safari on iPad.
Working from Northern Virginia US:
Windows 10 + Chrome
Windows 10 + Edge
Windows 10 + IE
Windows 11 + Chrome
Windows 11 + Edge
Ubuntu 18.04 + Chromium
Ubuntu 18.04 + Firefox
Your internet browser is probably forcing HTTPS. If you allow HTTP it should work fine.
I did notice that it was forcing https but I changed it to http and it still didn't work.
That worked. DNS propagation issue?
No when you're going to the conical name, it's forcing http instead of https. You need to turn that off in your browser
Your browser if forcing https when going to the conical name. Turn that off and it will be fine.
Why? This is the only website with this problem. My browser is acting like intended and this site worked in the past. You are suggesting a workaround and not a 'solution'.
The web site the doc's are on do not support https (no current certificate either purchased from a clearing house or self signed) so http is the only one available. So to reach it properly have your browser stop forcing https.
What browser are you using?
Chrome on MacOS.
Having similar problem with Chrome on Windows. I think a Chrome update may have caused it. My suggestion is to clear your browsing history. If you use incognito session do you experience the same issue ?
Using Incognito Chrome mode works. Clearing the cache make no difference on the regular session.
That means it's a cache/browser issue, as if it was on our side (other than having secure layer) would not have worked in incognito mode.