as soon as i try to enable the API password for my Hass.IO install I can no longer access the UI from either the external DuckDNS site or from the local IP address. I get the login page but I get an “unable to connect” error after entering the password.
I also dont think that my lets encrypt is setup correctly even though i did it via the Hass.IO addon “DuckDNS with lets encrypt built in”…
Any ideas?
anyone?
I have noticed that my phone can connect to Hass.IO remotely (using duckdns) without any issues. My laptop connects within the local network fine but when using an external network with my laptop (and trying via duckdns) I get the login screen requesting a password. Using the correct password it tries to connect but then gives me the
“unable to connect” error…
I dont know what to try
can someone please help me fix this issue?
Not sure if this helps at all, but I just moved my Raspberry Pi into a DMZ off my firewall, effectively moving it off the same LAN as my PC. Locally the login was working fine, but after the move my password seem to no longer work… I even tried commenting out the API_password to no avail. Turns out I had an application rule set to block high risk apps, and HA uses WebSocket which was in the high risk app category that I had set to block. I ended up making a white-list rule before this one and I can now login again.
I figured out part of my issue. I hadn’t put the ‘s’ on the end of ‘http’ where I list my duckdns address under the http: section of the config.yaml. I still however seem to have issues accessing Hass from a certain work wifi but I think that must be something with their security settings. I get the login and enter my password, it thinks for a while and then says ‘unable to connect’ just below the password box. If I use a different work wifi, I can log in without any issues at all… its a bit strange
Check for special characters in the password like []<>& - the reserved characters and escape them or use other ones.
nope. i don’t have special characters. like i say, it now works from some wifi connections, but not others so i think it might be something with that network