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 by navigating to Settings > System > Logs in the UI.

Open your Home Assistant instance and show your Home Assistant logs.

Home Assistant logs

When opening an add-on’s web UI page, Firefox users may see a “401: Unauthorized” message.

This issue affects users who use Firefox’s Browser & Privacy settings in Strict Mode. The mode can be set to Standard within Firefox’s settings, or an exception can be made for the Home Assistant website URLs, while keeping Strict mode enabled.

To create an exception, click on the shield icon in the address bar to the left of the current URL being used to reach Home Assistant, then toggle off Enhanced Tracking Protection for the site. You can confirm that the URL has been added to the list of exceptions from Settings > Privacy & Security > “Manage Exceptions…” in Firefox. Add an exception for both the local URL and the remote Nabu Casa URL.

This error usually occurs when the Home Assistant host has a bad IPv6 network configuration. Fixing the network configuration or disabling IPv6 on the host should resolve this error.

Users running a standard installation of Home Assistant, can disable IPv6 in the UI from the Supervisor > System > Host card.

Open your Home Assistant instance and show your Supervisor system information.

Click on “change” across from the IP address shown in the card, and expand the IPv6 dropdown. Choose the “disabled” option, save, and then reboot the host back by clicking “reboot” in the “Host” card.

This issue often affects VM installations. Follow the steps below from your hypervisor’s terminal console to disable IPv6:

  • Hit enter to interrupt the running log and login using root.
  • At the Home Assistant custom console, enter login.
  • Now at the host console, enter nmcli con show. Make note of the connection profile name. The default name is “HassOS default”
  • Enter nmcli con modify "HassOS default" ipv6.method disabled
  • Enter reboot

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": ["", ""]}' > /etc/docker/daemon.json

If 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