Alright, so you got all excited, tried to setup cloud and something went wrong? Don’t worry, here are some common issues and how to resolve them.
The first step in troubleshooting is to take a look at the logs. You can find them in the sidebar under developer tools. It’s the last one with an (i) icon.
This error occurs when Home Assistant is unable to communicate with our authentication server. We have been able to identify two different reasons for this issue to appear.
Pi-Hole will block the connection under certain configurations. Try temporarily disabling Pi-Hole to see if you are able to estbalish a connection.
The second reason the issue can occur is if Docker is misconfigured. This issue is especially common for people using the HOME ASSISTANT SUPERVISED installation on top of Ubuntu Bionic or another Linux installation. It is related to IPv6 being incorrectly marked as available.
The solution is to make sure that Docker uses a public available DNS server, such as those provided by Google or another of your choosing. As root, run:
mkdir -p /etc/docker
echo '{"dns": ["8.8.8.8", "8.8.4.4"]}' > /etc/docker/daemon.jsonIf you have an old version of a JWT library installed you can get an unknown error when you’re trying to login and in your error logs you see the following error:
AttributeError: module 'jose.jwt' has no attribute 'get_unverified_header'
To solve this you have to remove the following packages from the Python environment that runs Home Assistant and restart Home Assistant.
pip3 uninstall python-jose python-jose-cryptodome warrant