Repository navigation
Serve the Home Assistant OS link on port 80, with 8123 as its alternate - #26
Merged
Merged
Conversation
Home Assistant OS 2026.8 serves new installs on port 80. The template, readiness probe and onboarding hook move to 80, and postInstallAltPorts keeps 8123 for installs made before 2026.8. Re-vendors the blueprint schema for the new field.
6 of 7 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Home Assistant 2026.8 (2026-08-05) serves new Home Assistant OS installs on port 80 instead of 8123. Older installs keep 8123, and nothing on 8123 redirects. Every HAOS VM HexOS installs runs current Core, so it comes up on port 80, and the VM card's Launch link to
http://{ip}:8123opens a refused connection (reported on r/hexos on 2026-10-10).Changes:
home-assistant-os.json:postInstallUrlishttp://{ip}, and the newpostInstallAltPorts: [8123]lists the port older installs serve. eshtek/hexos-platform#2105 probes both and links to the one that answers.readiness.portis 80, so the mDNS probe can confirm a fresh install. Before this, it only got through on the guest agent's three-strike fallback.guestPortis 80, with 8123 as its alternate.bun run sync-schemafrom the hexos-platform#2105 branch (based onstaging@a8e2eb881). AddspostInstallAltPorts. It also brings staging'sgpuSharingcapability (eshtek/hexos-platform#2104), which nothing here uses.What changes for users once this syncs:
Promoting
stagingtoprodalso carries #24 (Plex on virtiofs), whose platform half, eshtek/hexos-platform#2043, reached prod in the 2026-10-10 release.Test plan
bun run validate: 29 blueprints and 32 apps, 0 errors. The one HAOS warning (id differs from the filename) was already there.bun run test-hooks: 81 pass.bun run typecheck: the same 5 errors in the vendoredvm-surfaces.tsas onstaging, none from this PR.postInstallAltPorts, and the hook resolves to port 80 with 8123 as its alternate.