Just upgraded my 0.37.1 install on a raspberry pi to 0.38. Using ssl to connect. After the upgrade I was not able to login via Safari. Works fine with Chrome.
Anyone else seeing this ?
Works for me in Safari
I have not yet upgraded
What specific safari are you referring to?
on an iOS device, a Mac, something else?
What version safari?
Tried both iOS and Mac (sierra - latest).
Did you empty the caches and restart Safari?
Emptied cache and restarted Safari. Problem only exists on mac book I have. IOS devices working now. Other macs OK with Safari. Must be localised issue.
Weird thing is that my 0.37 instance works fine. Just the 0.38 has the problem from this particular machine.
I’ve got the exact same problem on iOS, with safari (iOS 10.2.1). Already cleared cache, etc. after putting in the correct password, I get the message “unable to connect”. Also getting the exact same message on Chrome on iOS (Chrome version 56.0.2924.79). Chrome on MacOS Sierra works fine, without issue. This is only after upgrading to 0.38.1, all previous versions worked fine.
Chrome works fine for me. Also try a different machine if you can. I still have this issue on one laptop. Other machine is fine.
Chrome works fine for me on 2 MacOS machines, but neither Chrome nor Safari work on iOS. Either on my phone, or my iPad, both get the same exact error.
Wanted to chime in as well. I was going to start a new thread but just found this one. I have similar issues not being able to login neither via Safari or Chrome on my iPhone (iOS) I can only login through Chrome on my MacBook. Hoping that a hotfix will be issued for this problem. I’ll wait before I revert back. Thanks
So… I just discovered something interesting. On my iPhone if I try to load up the UI via safari or chrome, put in the password, I always get “unable to connect”. But if I disable wifi, and hit the UI via safari from my public URL, put in the password, it logs me right in! Can someone else verify this please?
You’re onto something. Think you can eliminate the wifi or external network connection. The issue I see is if I use my external DNS address (https://myname.duckdns.org:8123) to connect it works fine. If I use the internal IP address (https://192.168.1.35:8123) it fails. I think its related to the addressing method rather than the network connection.
Try using the two address for your network on the device using WiFi.
1 Like
I’ve got the same experience here. iPhone connected to wifi.
Public URL, logs right in.
Private URL, “unable to connect”.
Makes me wonder if the new version is doing any SSL validation against the URL that presents it. In either case, the same SSL cert is used. From the Public side, the cert is valid. From the private side, it’s invalid (because the URL doesn’t match the cert).
1 Like
Note … running 0.38.1
Not going to install 0.38.2 … will wait to next update.
Have the same problem/feature after updating to 38.2, Firefox works fine but Safari does not. Based on previous feedback I tried hitting the outside hostname/IP which matches my certificate and it works from Safari. Looks like xstrex is correct, Safari will not connect if cert does not match…
1 Like
Anyone know if a fix is planned for this?
I have the same issue. I have set up duckdns and let’s encrypt. I can connect from an external network from my computer and iphone via “https://xxxxx.duckdns.org:8123”. I see no issue there. This link does not work within my network. Instead I can connect internally from my computer with “https://internal-ip-address:8123”, however when I try to access hassio on my phone from within my network with the internal address, I enter my password as usual, the login screen loads for a while, then spits me right back to the login. I am unable to login. It is odd that I can access hassio from the computer but not the phone. I’m not sure what to make of it. It seems this is a common issue. Does anyone have a potential fix?