Quick answer
Check the address first. Use http://homeassistant.local:8123 or http://<IP>:8123, and remember the :8123 port. Then confirm the device is powered on and has finished starting. If the page still does not load, the cause is usually the network, a Home Assistant that is restarting, or a remote-access setting.
Check the address and port
- Include port
:8123in local addresses. - If you set SSL in the
http:section ofconfiguration.yaml, usehttps://. Plainhttp://will fail. - If
homeassistant.localdoes not resolve, use the IP address. Name lookups fail on some Android phones, VPNs, VLANs and Windows setups. - Check the IP for typos. A wrong address reaches a different device or nothing at all.
- If the page is blank or keeps reloading, try a private browser window. Old cached files can cause this.
Confirm the device is running
- Check that the device has power and a network connection, usually shown by its link or network light.
- On Home Assistant OS, the first start can show “Preparing Home Assistant” for up to about 20 minutes. Wait before you assume something is broken. On HA OS, the Observer page (usually on port 4357) shows host and Supervisor health.
- On a Raspberry Pi, a weak power supply causes restarts and boot loops. Use a 5V 3A supply for a Pi 4, and a 5V 5A supply for a Pi 5. A failing SD card can cause the same symptoms.
Find the current IP address
A router can assign a new address after a restart, so a bookmarked IP can stop working. To find the current one:
- Check the list of connected devices on your router’s admin page.
- Or check the console on a monitor attached to a Home Assistant OS device.
Then set a DHCP reservation on the router. That keeps the same address for the device every time.
Check your network
- Your computer or phone must be on the same network as Home Assistant. Guest Wi-Fi, separate VLANs and “client isolation” settings can block access between devices.
- If Home Assistant connects over Wi-Fi, a weak signal or roaming between mesh access points can cause brief drops. A wired Ethernet connection is more reliable.
What “Unable to connect. Retrying” means
When the browser shows “Unable to connect to Home Assistant. Retrying”, Home Assistant Core is usually restarting or has crashed. Give it a few minutes. If it keeps failing, check the logs.
A successful ping only shows that the host is up. It does not show that Home Assistant Core is running.
Remote connections that fail
If the address works at home but not from outside:
- A “400: Bad Request” error through a reverse proxy usually means
trusted_proxiesis missing. See how to set up secure remote access. - An expired certificate, a changed public IP address, or CGNAT on your internet connection can block remote access.
- With Home Assistant Cloud, check that remote access is still turned on.
- In the companion app, check the internal and external URLs.
Locked out by failed logins
Home Assistant can ban an IP address after repeated failed logins. The bans are stored in ip_bans.yaml. Before you edit that file, make a copy of it. Then remove the entry for your address and restart Home Assistant.
When the interface loads but shows errors
A YAML error can stop the interface from loading. From the console, two commands help:
ha core checkchecks the configuration.ha core logsshows the Core log.
If Home Assistant still will not start, try safe mode. Restart and reboot options covers how to do that. For reading the log, see how to find and read Home Assistant logs.
When to restore a backup
Restoring a backup is the last resort, because you lose any changes made after that backup. Reinstalling is rarely needed. Most cases come down to the address, the IP or a configuration problem. If you do need a restore, see how to back up and restore Home Assistant.