Silverbullet no longer works without HTTPS #762
Description
Describe the bug
The latest version of the v2 Silverbullet image tag cannot
Environment
- Ansible-NAS revision (
git rev-parse --short HEAD): 36e2338 - Ansible-NAS Docker version (
docker --versionon the Ansible-NAS box): Docker version 24.0.2, build cb74dfc - Silverbullet docker image: sha256:927e83fa076b335ec0bcf45fbf82530895ba1318d9728182c4d37353e949756a
- Latest Silverbullet container logs:
Will run SilverBullet with UID 0, inferred from the owner of /space (set PUID environment variable to override)
2025/11/21 13:34:34 User authentication enabled for user "me" with lockout limit 10 and lockout time 60s
2025/11/21 13:34:34 Local shell command execution enabled for ALL commands.
2025/11/21 13:34:34 SilverBullet is now running: http://0.0.0.0:3000
- Are you running the playbook from a remote box or the Ansible-NAS box itself? remote box
Expected behavior
We should be able to browse Silverbullett via HTTP as we could previously.
Actual behavior
Browser fires an alert You are likely accessing SilverBullet via HTTP (rather than HTTPS or localhost), this is not a supported configuration. See https://silverbullet.md/TLS and shows a blank page.
Steps to reproduce
Set silverbullet_image_version: v2 in group vars and run the playbook.
Playbook Output
Playbook runs successfully, but the resulting Silverbullet container doesn't behave as expected.
Additional context
From reading https://silverbullet.md/TLS the SSL tunnel option seems like a less than ideal UX for a system like a NAS/homelab. What would be the downside to creating HTTPS endpoints for services that aren't exposed externally? Most folks must be using internal DNS or their hosts file to access their NAS via a domain name 🤔