Unable to connect

Configuration
1

I’m having an issue trying to connect to the gui remotely.

I use

mydomain.com:8123

to connect.

It works, from inside my lan
It works from my 4G phone - using the “3” network in the UK

It used to work from my Office PC (totally different network) but now, I get a login page (I have no password set) which “spins” and then returns an error “Unable to connect” with a logo and a password entry “box”

I have tried different browsers - Firefox, Chrome, IE11, Edge - no difference. I have cleared the cache.

It’s driving me mad, because I’m having to VNC into my local lan and use a PC on my network - far from ideal.

Any ideas anyone?

2

First if all, you should implement some level access control; without that anyone who happens to know the address can remote control your home.
You could check if there are any requests from your Office PC to the HA server failing. Maybe there is a corporate firewall that blocks certain requests. In Chrome for example, check with the ‘Developer Tools’, tab ‘Network’, reload the page (after clearing the cache again). That login page for example appears if websocket requests don’t come through.

3

Thanks exxamalte

I know I should add some authentication - and I will do way before I use it in any serious capacity, just learning and playing with it for the moment.

So, I tried in Chrome - with the developer tools, got a bunch of websocket entries at the top - all of which say “Finished” under status, and “Pending” under Time.

There are 12 errors - 11 say

failed: Establishing a tunnel via proxy server failed.
the other says
Uncaught (in promise) DOMException: Only secure origins are allowed (see: https://goo.gl/Y0ZkNV).

If I try to reach the url
ws://mydomain.com:8123/api/websocket I get an error:
ERR_DISALLOWED_URL_SCHEME

If I try without the ws:// I get:
No WebSocket UPGRADE hdr: None
Can “Upgrade” only to “WebSocket”.

I’m guessing this is an issue with my corporate proxy, but I’m sure it worked before, with an earlier version, when I was running it on a Pi 2 (I’m now on a Pine64)

4

Don’t worry about those errors - you normally can’t establish a websocket connection by typing a ws:// address into the address bar.

That sounds more suspicious. When you say that it was working with an earlier version of HA, it might be some newly introduced frontend library that now fails with your corporate proxy.

5

I think I need to reload HA back onto the Pi and see whether that cures it - I haven’t yet repurposed it.

6

I am also having this message only on one PC in home. I’ve tried Chrome, IE, and Edge and get the same results. The Homeassistant logo and a spinning wheel. I even left it overnight and it’s still spinning. When I connect from my phone, tablet, or laptop I have no issues accessing the page.

I’ve checked ports, firewall, and can’t really narrow down what this might be!

*edit - This is a brand new install of Hassbian. No changes done whatsoever. I’ve even reloaded the image to make sure!