Home Assistant defaults to port 8123. That is fine, but it forces URLs like:
https://assistant.home:8123
If you already have local HTTPS working (for example with a self-signed cert), switching to port 443 lets you use the cleaner, standard URL:
https://assistant.home
What changes (and what does not)
- Home Assistant will still serve the same UI.
- Only the listening port changes from
8123to443. - You still need a certificate configured in Home Assistant.
Step 1: Make sure port 443 is available
Port 443 can only be used by one service on that machine.
Some quick checks:
- If you run something like Nginx, Caddy, Traefik, or another web UI on the same host, it might already be on
443. - If
443is taken, Home Assistant will fail to start (or will not bind to the port).
Step 2: Update configuration.yaml
Edit your configuration.yaml and update the http: block.
Example (matching the self-signed approach from my previous note):
http:
ssl_certificate: /ssl/homeassistant.crt
ssl_key: /ssl/homeassistant.key
server_port: 443
Save the file.
Step 3: Restart Home Assistant
Restart Home Assistant via:
Settings -> System -> Restart
After the restart, Home Assistant should be reachable at:
https://assistant.home
Step 4: Test and clean up old URLs
- Your old URL
https://assistant.home:8123will stop working (unless you also keep something listening on 8123). - Update bookmarks, dashboards, or apps that still point to
:8123.
If your browser behaves oddly, test in a private window and clear site data for assistant.home.



Leave a Reply