BluOS web interface now requires additional ports

Robert

• 24. Oktober 2026 05:28

Previously, the BluOS web interface worked over standard HTTP/HTTPS ports. Recently, the interface started getting stuck on a black screen with a loading spinner, although direct access to the player still works.

Investigating the issue in the browser's developer tools revealed that the web interface now makes API requests over HTTPS on port 11005, which redirects to port 11007. These additional ports must also be reachable for the interface to finish loading.

This creates problems in network environments with restrictive firewall rules or with reverse-proxy setups, where access is deliberately limited to specific ports (i.e. 80/443). A web interface that previously worked over standard HTTP/HTTPS now depends on additional ports being accessible.

Was this a recent change in BluOS, and is this behaviour intentional?

0

• 

  Seppi Evans

  • 24. Oktober 2026 07:44

  I must confess to not using the web interface but do recall that 11000 upwards is used for BluOS API / multi room sync.

  I don’t think there is anything to worry about but best wait for support to confirm.

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.