OPEN BETA · PUBLIC STATUS
Known issues. Visible progress.
Beta testing catches real problems. Here's what we know, what has been addressed in a release, and where to report something new. GitHub holds the detailed technical record; this page gives the quick overview.
Last reviewed: 8 October 2026 · Brimstone Core 1.0.1 · This is a curated summary, not a live feed. Always check GitHub for the newest status.
ADDRESSED IN RELEASES
Previous fixes and current QA notes.
Install the current Core package to pick up these changes. Existing installations are not updated automatically.
INSTALLER · FIX RELEASED
Debian installer could not find its updater
The installed command was resolving its symbolic-link directory instead of the packaged files. The installer now resolves the real script path and checks required assets before commissioning.
NETWORK · FIX RELEASED
Core inaccessible by LAN IP or core.local
VM installations could redirect numeric-IP requests into an HTTPS handshake failure. Docker bridge addresses could also interfere with mDNS advertising. Version 1.0.1 adds LAN-interface detection, IP routing and core.local configuration.
CURRENT LIMITATIONS
Things testers should know.
These are remaining constraints or items awaiting testing, not claims that every user will encounter them.
HTTPS · LOCAL CERTIFICATES
Local HTTP / HTTPS certificate trust
Core can use a locally issued certificate for LAN HTTPS. Your browser may ask you to trust that local certificate authority. Do not disable certificate verification globally. Keep private remote access behind an appropriately configured trusted connection.
DISCOVERY · NETWORK-DEPENDENT
core.local across networks
mDNS generally works only on the same local network. Some NAS virtual switches, routed VLANs and firewall configurations block multicast discovery. Use the Core LAN IP if the hostname cannot be resolved.
AUDIO · TESTING
Multichannel audio hardware
Multichannel output from a virtual machine depends on audio-device passthrough or a suitable network playback endpoint. Specific 5.1/7.1 hardware paths still need testing; they are not yet verified for every setup.
INSTALLATION · REQUIREMENTS
Full virtual machines only
Debian 13 bare-metal systems and full VMs are the supported installation approaches. For a VM, allocate at least 4 vCPUs and 8 GB RAM. LXC containers are not supported.
For the remaining development and testing notes, see the Beta 1 installation issue ledger.
REPORT A BUG
Found something new?
Tell us the Core or Control version, device/platform, expected behaviour, actual result and steps to reproduce. A screenshot or a carefully redacted log can help.
Private support request
Best for most beta testers, especially when the problem involves log files, network details, account information or anything you do not want public.
GitHub issue
Best for technical reports that are safe to discuss publicly. Check existing issues before opening a duplicate and include clear reproduction steps.