Why Can't I Access My Home Assistant Remotely?
- No remote-access method configured
- Nabu Casa not enabled/subscription lapsed
- Reverse proxy/SSL misconfigured
Problem Description
You can't reach Home Assistant remotely — it works on your home network but not away from home. Remote access needs a path from the internet to your HA instance, typically Nabu Casa (Home Assistant Cloud) or a self-hosted reverse proxy/VPN, so most issues are that path not being set up or misconfigured.
Why This Happens in Real Homes
Home Assistant only reaches the outside world if you give it a path — the simplest is Nabu Casa (Home Assistant Cloud), which handles SSL and connectivity for a subscription; the DIY route is a reverse proxy with your own certificate, or a VPN back home. "Works locally but not remotely" means that path isn't set up or is broken.
Start by choosing a method: enable Nabu Casa, or set up a reverse proxy/VPN. If you're self-hosting, many ISPs use CGNAT that blocks port forwarding entirely — a VPN or Nabu Casa sidesteps it. Set the correct external URL in HA, use DDNS for a changing IP, and configure trusted_proxies if you run a proxy.
Symptoms
- Cannot connect away from home
- Works on local WiFi only
- Remote URL times out
- Nabu Casa not connecting
- SSL/certificate errors
- App cannot reach HA remotely
- Port forwarding not working
- Intermittent remote access
Recognize these? Here's what usually causes it.
Common Causes
- No remote-access method configured
- Nabu Casa not enabled/subscription lapsed
- Reverse proxy/SSL misconfigured
- Port forwarding blocked (CGNAT/ISP)
- Dynamic IP changed (no DDNS)
- Firewall blocking
- Wrong external URL in HA
- trusted_proxies not set for a proxy
Most fixes happen in the first 3 steps.
Nabu Casa subscription supports Home Assistant development while providing easy remote access.
Tools & Requirements
These tools will help you complete this fix.
As an Amazon Associate we earn from qualifying purchases.
Step-by-Step Solution
Use Nabu Casa for the simplest remote access
Nabu Casa (Home Assistant Cloud) is the official subscription service ($6.50/month) that provides encrypted remote access without port forwarding, dynamic DNS, or SSL certificate management. In Home Assistant, go to Settings > Home Assistant Cloud > sign up or log in. Once connected, your instance is accessible at a unique URL (e.g., https://xxxxxxxx.ui.nabu.casa). The connection is end-to-end encrypted through Nabu Casa relay servers. This is the recommended method for most users.
Set up DuckDNS and Let's Encrypt for free remote access
For free remote access without Nabu Casa: install the DuckDNS add-on (Settings > Add-ons > Add-on Store > DuckDNS). Create a free DuckDNS subdomain at duckdns.org. Enter your DuckDNS token and domain in the add-on config. The add-on automatically obtains an SSL certificate from Let's Encrypt and keeps your dynamic IP updated. Then set up port forwarding on your router: forward external port 443 to your Home Assistant IP on port 8123.
Configure port forwarding on your router
Log into your router admin page (typically 192.168.1.1 or 192.168.0.1). Find the port forwarding section (sometimes called NAT, Virtual Server, or Port Mapping). Create a rule: external port 443 → internal IP of your HA device → internal port 8123. Protocol: TCP. Save. Your Home Assistant is now accessible at https://yourname.duckdns.org from outside your home. If your ISP uses CGNAT (common with 5G/cellular ISPs), port forwarding does not work — use Nabu Casa or a VPN instead.
Use a VPN as an alternative
A VPN (WireGuard or Tailscale) provides remote access without exposing Home Assistant to the public internet. Install the WireGuard or Tailscale add-on in Home Assistant. Set up VPN clients on your phone and laptop. When connected to the VPN, your phone acts as if it is on your home network — access Home Assistant at its local IP. Tailscale is the easiest: install the add-on, authenticate with your Tailscale account, and your HA device gets a Tailscale IP accessible from all the hubs.
Secure your remote access
Regardless of method: enable multi-factor authentication for all Home Assistant user accounts (Profile > Multi-Factor Authentication). Use strong, unique passwords. Keep Home Assistant updated — security patches are released regularly. If using port forwarding, never forward port 8123 directly without SSL — always use HTTPS (port 443 with a valid certificate). Check Settings > System > Logs for unauthorized login attempts. Consider using the IP Ban feature (auto-bans IPs after multiple failed login attempts).
Quick Solutions
Still having issues? This is usually the deeper cause below.
If this comes back after following these steps, check whether a recent app or firmware update reset a default setting — the fix works, but the setting gets reverted silently.
Place your hub in a central location in your home, elevated off the floor and away from your WiFi router by at least 3 feet. This provides the best Zigbee and Z-Wave signal coverage to all corners of your house.
Home Assistant issues that only appear after restart are a well-known quirk — triggers that require prior state history simply can't fire until that history rebuilds.
- No remote-access method configured
- Nabu Casa not enabled/subscription lapsed
- Reverse proxy/SSL misconfigured
- Port forwarding blocked (CGNAT/ISP)
- Dynamic IP changed (no DDNS)
Before you go — try one of these (they fix most cases).
Most popular upgrades chosen by Home Assistant owners.
Home Assistant Connect ZWA-2 | Connect Z-Wave devices to ...
Zooz 800 Series Z-Wave Long Range GPIO Module ZAC93 LR (U...
Home Assistant Connect ZBT-2 | Connect Zigbee, Thread, or...
As an Amazon Associate we earn from qualifying purchases.
Official Manufacturer Manual
Home Assistant provides official product documentation through their online manual rather than downloadable PDF. Access setup guides, troubleshooting steps, and product specifications for your Home Assistant.
Source: home-assistant.io
Need More Help? Home Assistant Support
Note: The contact information below connects you directly to Home Assistant's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.
Accessories owners commonly pair with Home Assistant.
Amazon Smart Plug, Works with Alexa, Simple Setup, Endles...
TP-Link WiFi Extender with Ethernet Port, Dual Band 5GHz/...
Kasa Smart Plug, Matter Compatible, Energy Monitoring, Co...
As an Amazon Associate we earn from qualifying purchases.
