From 65233d1291db1a279430e0b4a1534fa3f0ef4ee8 Mon Sep 17 00:00:00 2001 From: Alexandre <44178713+alexbelgium@users.noreply.github.com> Date: Mon, 17 Aug 2026 07:55:10 +0200 Subject: [PATCH] docs(filebrowser_quantum): stop advertising direct access on port 8071 (#2981) config.yaml declares ingress_port: 8071 but no ports: key, so nothing is published to the host network. ingress_port is the internal port the Supervisor ingress proxy connects to on the add-on's private IP, and Home Assistant only renders the Network card for add-ons that declare ports:. Direct access at :8071 has therefore never worked; the README was carried over from the sibling filebrowser add-on, which does declare ports: 8080/tcp: 8071. Correct the three README claims rather than publishing a port, since the app is configured with server.baseURL set to the ingress entry and would not serve correctly on a plain published port without further work. Closes #2978 Co-authored-by: claude[bot] <41898282+claude[bot]@users.noreply.github.com> Co-authored-by: Claude Opus 5 --- filebrowser_quantum/CHANGELOG.md | 3 +++ filebrowser_quantum/README.md | 6 +++--- filebrowser_quantum/config.yaml | 2 +- 3 files changed, 7 insertions(+), 4 deletions(-) diff --git a/filebrowser_quantum/CHANGELOG.md b/filebrowser_quantum/CHANGELOG.md index 7563d190cd..981d8c0490 100644 --- a/filebrowser_quantum/CHANGELOG.md +++ b/filebrowser_quantum/CHANGELOG.md @@ -1,4 +1,7 @@ +## 1.5.1.1 (2026-08-17) +- Documentation: the add-on is Ingress-only and does not publish port 8071, so the README no longer advertises direct access at `:8071` + ## 1.5.1 (2026-08-08) - Update to latest version from gtsteffaniak/filebrowser (changelog : https://github.com/gtsteffaniak/filebrowser/releases) diff --git a/filebrowser_quantum/README.md b/filebrowser_quantum/README.md index adb1145358..8229500e15 100644 --- a/filebrowser_quantum/README.md +++ b/filebrowser_quantum/README.md @@ -42,11 +42,11 @@ comparison to installing any other Home Assistant add-on. 1. Click the `Save` button to store your configuration. 1. Start the add-on. 1. Check the logs of the add-on to see if everything went well. -1. Access the web UI through the sidebar or at `:8071`. +1. Access the web UI through the Home Assistant sidebar. ## Configuration -The web UI can be found at `:8071` or through the Home Assistant sidebar when using Ingress. +The web UI is reached through the Home Assistant sidebar (Ingress). This add-on does not publish a port on your network, so it has no **Network** section in its configuration page and is not reachable at `:8071`. **Default credentials:** - Username: `admin` @@ -69,7 +69,7 @@ The web UI can be found at `:8071` or through the Home Assistant sideba ## Setup 1. Start the add-on and wait for it to initialize. -1. Access the web interface through the Home Assistant sidebar or at `:8071`. +1. Access the web interface through the Home Assistant sidebar. 1. Log in using the default credentials: - Username: `admin` - Password: `admin` diff --git a/filebrowser_quantum/config.yaml b/filebrowser_quantum/config.yaml index 7fc51369bd..df66a9069c 100644 --- a/filebrowser_quantum/config.yaml +++ b/filebrowser_quantum/config.yaml @@ -114,4 +114,4 @@ schema: slug: filebrowser_quantum udev: true url: https://github.com/alexbelgium/hassio-addons -version: "1.5.1" +version: "1.5.1.1"