Home Assistant without port 8123: what changed and whether to change the old address

Home Assistantsmart homehome networking

A model house connected by an Ethernet cable to a home router

A shorter address does not mean the old one is broken

Home Assistant is a platform for managing smart-home devices and automations through a local browser dashboard. If an old bookmark with :8123 works while the 2026.8 notes show no port number, that is not evidence of a fault.

Home Assistant OS is a ready-made, minimal operating system for running Home Assistant on a dedicated device or virtual machine. This option does not require separate administration of a general-purpose operating system.

According to the official release notes, the 2026.8 change applies only to new Home Assistant OS installations. Addresses and ports on existing systems do not change automatically. If access works, do not reconfigure the system merely to shorten its address.

A short glossary: parts of the address

Break down http://homeassistant.local:8123:

  • http is the protocol, or the rules for exchanging data with the web interface;
  • homeassistant.local is the hostname, or network name that resolves to an IP address;
  • 8123 is the network port, a number that tells the device which service should receive the connection.

An IP address is a device’s numeric address on the local network. Depending on the setup, it may also open the web interface. When sharing an address with an AI service or another person, use a masked example such as 192.168.x.x. Do not include passwords, tokens, or a complete configuration.

When no port number appears, the browser normally uses 80 for http and 443 for https. This is a general rule for web addresses. The release notes confirm a narrower fact: the default address of a new Home Assistant OS installation in 2026.8 does not require :8123.

Three situations and safe decisions

SituationExpected behaviorSafe decision
New Home Assistant OS installationThe default address does not require :8123Use an address verified on your local network
Existing systemIts address and port do not change automaticallyChange nothing if access works
Manually configured port or proxyYour settings determine the addressCheck the setup documentation or involve a specialist

In Home Assistant 2026.8, the web server port can be changed through the interface. After applying new settings, the system gives you five minutes to confirm access. Without confirmation, it restores the previous settings and restarts. If it cannot apply the new settings, Home Assistant restores the previous ones immediately.

This mechanism reduces risk, but does not make a change necessary. Changing the port may require updates to bookmarks, the mobile app, and connected tools. The address format alone does not prove which version is installed.

If a proxy sits between the browser and Home Assistant

A reverse proxy receives a request at one address and forwards it to Home Assistant at another. The trusted proxies setting identifies proxy addresses or networks whose forwarded information about the original client Home Assistant may trust.

In this arrangement, the browser address also depends on proxy settings. Do not create port-forwarding rules based only on general advice or expose Home Assistant directly to the internet. If no other verified address exists or the arrangement is unclear, consult a specialist.

Checklist: working safely with AI

AI can organize observations, but a confident answer is not proof. One release source is insufficient grounds for changing a home network safely.

  1. Understand. Give AI the official excerpt, confirmed installation type and version, and a masked address. It may explain terms, not infer a version or recommend public access. Stop if unknown; save a fact list and verify it against the notes.

  2. Inspect. Give it masked addresses, the browser error, connection type, and results. Compare only a known hostname, local IP, and port—no scans, credentials, or changes. Stop for a public IP or warning; save and repeat a local test log.

  3. Plan. Give it the test log, install type, working address, and known proxy or custom-port details. Ask for safe options, never commands or forwarding rules. Stop if access fails; keep a return-to-working-address plan and compare it with the notes.

  4. Act. With a verified plan, record a no-change decision or a specialist handoff; do not alter the system, network, or internet exposure. Stop before interrupting access, and verify that the working address still opens.

  5. Verify. Compare a masked test log with the three situations above. AI text, HTTP, or a screenshot is not proof. Stop if devices disagree; repeat locally in another browser or device and record confirmed versus open conclusions.

  6. Explain. Use verified facts and a masked log to state what works and whether change is needed. Do not hide uncertainty. Stop if type, port, or proxy is unclear; check the conclusion against the notes and remove private data before sharing.

The main rule is simple: the presence of :8123 is not an error by itself. Reliable local access matters more than a cosmetically shorter address.

Sources