Brand new install of Hassio on Pi3 using mac and safari
have added configurator add on, then duckdns add on, at which point http stopped working and https did not start working
at this point Duckdns did not work so I made a post, but Duckdns seems to now work, this seems to be a new problem, hence the new post (hope that’s ok)
accessed HA through duck dns, installed SSH.
Can now connect to HA through duckpins, ssh and samba share but if i enter https://hassio.local:8123 it shows a Home Assistant logo and:
Unable to connect to Home Assistant.
RETRY
On a private browser if I connect to https address it asked me to logon, I entered login details again and get the same message, so the HA install is working, but not in safari.
next step I try Chrome, I get a security warning but going through that I CAN access it using https so what is the matter with safari?
I notice after typing https://hassio.local:8123 that it actually diverts to /lovelace is it something to do with this? or a security setting in safari?
I thought https was for duckdns only, but I cannot access my Hassio install in safari using HTTP or HTTPS.
Seems odd that I have changed something and Safari now does not work, whereas it worked prior to installing the duckdns addon.
I can access my Hassio install in chrome using https://hassio.local though so how is that working, or is chrome just removing the S and letting me proceed?
The certificate for https access is only for duckDNS. However it also disables http access to the IP address and hassio.local as well.
You installed SSL certificates when you setup duckdns. http will no longer work. You have to use https and the certificate for this is only valid for duckdns, not the ip address, not hassio.local. So if you try to go to https ://hassio.local you will get a certificate error (which you can chose to ignore in most browsers). If you try to go to http ://hassio.local the web server in HA will close the connection (“ERR_EMPTY_RESPONSE”).
At some point you have told Chrome to ignore the invalid certificate. If you delete your history in Chrome (or use incognito mode) you will have to do this again.
You should be able to get Safari to ignore invalid certificates too. However if you can’t do this then just use https://your_domain.duckdns.org in Safari.
Just a little note on this as it was bugging me. Safari is my browser of choice, it seems daft I cannot just use it without going through Duckdns, but I have tried a private browsing, clearing the hsts cache etc and still I go to https://hassio.local:8123 and it loads the logon, lets me logon and then goes to load into the main screen then shows the unable to connect screen.
Chrome still works, but I am surprised its not bugging more people.
Ok, complete cache and history clear, then back to https: it asks me about the invalid certificate, gave me the option to visit and this time a message saying “this needs permission to modify your settings”.
entered password, and it let me through and logged me in properly!
Sorry if the topic is a bit different, I ask help because suddenly I cannot access to my hassio instance with Chrome ignoring security warning of certificate (I have duckdns addon), before I was able to access writing my raspberry local ip:8123/lovelace, ignoring security warning, now with Chrome on Windows I access only using duckdns ip, with Firefox I can access also with local ip, I cleared cache and even setted default config in Chrome but nothing, prompt me fir user and password of my hassio, always “Unable to connect to Home Assistant”, user and password are correct, tried also to add trusted networks, nothing at all, the strange is this has always worked till today.
I have a very similar situation (DuckDNS installed; Hassio on an RP4). I’d like to use the iOS Home Assistant app (or HassApp if need be) to access remotely and send home my location data, for example.
How can I configure things to allow the app to talk to Hassio both at home and away from home?
When I try “https://MYSITE.duckdns.org” about 5 seconds goes by and thereafter I get “Connection could not be established”.
When I try “http://MYSITE.duckdns.org”, so just http - then I get a login screen. But that screen looks nothing like the Hassio login (it is in Danish)
Hi @CeeWeee,
I did get things working now. There is a newer version of the app that can detect whether it should use the external url or the local IP. I use the duckdns plugin and port forwarding with my modem and router.
No promises when I can get back to you, but feel free to reach out.
Are you guys able to access your HASSIO with the local network IP instead of the duckdns domain?
A few weeks ago Chrome started interfering with the login process. I have my network set as a trusted network, but as soon as I submit my username, all I get is the HASSIO logo with a “retry” link below it.
By looking at the browser’s console it seems that the problem is related to the SSL certificate:
WebSocket connection to 'wss://xxx.xxx.xxx.xxx:8123/api/websocket' failed: Error in connection establishment: net::ERR_CERT_COMMON_NAME_INVALID
e @ core.2755f59a.js:1
lovelace:1 Uncaught (in promise) 1
app.a9501bd7.js:20473 Uncaught (in promise) DOMException: Failed to register a ServiceWorker for scope ('https://xxx.xxx.xxx.xxx:8123/') with script ('https://xxx.xxx.xxx.xxx:8123/service_worker.js'): An SSL certificate error occurred when fetching the script.
This does not happen with Firefox (I’m able to login via the local IP).
Took me a while, but figured this one out (at least on my own setup).
Posting for future time travelers who may have the same issue:
My Setup:
https://(homeassistant).duckdns.org with SSL from NGINX proxy manager – can access using SSL on Chrome, Firefox, etc. on various machines with no issues.
BUT when visiting the same URL with Safari on OSX, I am greeted with the familiar login screen, then subsequently the “Unable to connect to Home Assistant – RETRY” page. Only in Safari, other browsers on the Mac successfully log in.
Solution:
Some sleuthing found an error being thrown in the JavaScript Console in Safari: “content blocker prevented frame displaying https://(website) from loading a resource from wss://(website)/api/websocket”
Safari --> ‘Settings for This Website…’ --> untick ‘Enable content blockers’ fixed everything
