Problem after update

v2: Troubleshooting
1

Hello,

I upgraded Silverbullet today to 2.1* version and after the update I have an issue.
Login page is loading but afte this blank white page is shown and nothis is visible. Info on brower console:

client.js:29 [Client] TypeError: Cannot read properties of undefined (reading 'digest')
    at tG (client.js:70:10381)
    at nV (client.js:70:10553)
    at Md.init (client.js:342:254229)
    at client.js:345:2453

Logs:


silverbullet-1  | Will run SilverBullet with UID 1000, inferred from the owner of /space (set PUID environment variable to override)
silverbullet-1  | Creating 'silverbullet' group (with GID 1000) and 'silverbullet' user (with UID 1000) inside container
silverbullet-1  | Running SilverBullet as user configured with PUID 1000 and PGID 1000
silverbullet-1  | 2025/10/30 19:51:58 User authentication enabled for user "admin" with lockout limit 10 and lockout time 60s
silverbullet-1  | 2025/10/30 19:51:58 Local shell command execution enabled for ALL commands.
silverbullet-1  | 2025/10/30 19:51:58 SilverBullet is now running: http://0.0.0.0:3000
silverbullet-1  | 2025/10/30 19:53:02 Unauthorized access to /.config, redirecting to auth page
silverbullet-1  | 2025/10/30 19:53:02 Unauthorized access to /.fs/Library/Std/APIs/Schema.md, redirecting to auth page
silverbullet-1  | 2025/10/30 19:53:02 Unauthorized access to /.fs/Library/Std/Config.md, redirecting to auth page
silverbullet-1  | 2025/10/30 19:53:02 Unauthorized access to /.fs/CONFIG.md, redirecting to auth page
silverbullet-1  | 2025/10/30 19:53:04 Unauthorized access to /favicon.png, redirecting to auth page
silverbullet-1  | 2025/10/30 19:57:14 Unauthorized access to /.config, redirecting to auth page
silverbullet-1  | 2025/10/30 19:57:14 Unauthorized access to /.fs/Library/Std/APIs/Schema.md, redirecting to auth page
silverbullet-1  | 2025/10/30 19:57:14 Unauthorized access to /.fs/Library/Std/Config.md, redirecting to auth page
silverbullet-1  | 2025/10/30 19:57:14 Unauthorized access to /.fs/CONFIG.md, redirecting to auth page
silverbullet-1  | 2025/10/30 19:57:15 Unauthorized access to /favicon.png, redirecting to auth page
2

Not sure why this would break with 2.1, but are you accessing SB via http by any chance instead of https? Because then all crypto APIs are disabled. You have to use https.

3

You are right. It was an issue, strange because earlier it was working on http.
Issue solved. Thank you.

4

Yeah, http was never a supported option but still people miss that part and mostly it work(ed). I may have to give more vocal errors that this is going to be more and more of a problem since more functionality may rely on https-only features like crypto, clipboard access etc. For the record, these are browser-restrictions not SilverBullet ones.

5

There might be more of an issue. It appears to even impact the wiki itself

image
image1619×997 97.3 KB

This happens when clicking on a link. It blocks the link and gives a JS error

6

Does this still happen after a reload or two?

7

Interesting. I hit the same for my local-only setup (which simply followed the local Docker setup guide at: Docker). Did not even know that I am supposed to use https for the ~last year of usage.

Probably need to figure out some kind of localhost TLS setup now…

8

Let me guess, you are on a mac/iphone/safari?

Because this also happen to me when browsing from an apple device, and try to open an image, instead of opening or viewing it, it gives me a similar error:

Failed to navigate:undefined is not an object (evaluating 'this.iframe.contentWindow.silverbullet.dispatchEvent')

IMG_3857
IMG_38572154×992 268 KB

or maybe mine is an unrelated issue?

9

It’s this issue Document editors don't work on safari · Issue #1627 · silverbulletmd/silverbullet · GitHub

But the commentator above seems to be using firefox

10

If you’re using localhost, you don’t need to use https, just anything other than localhost.

11

Hm. I am using http://0.0.0.0:3000/ but get the error there:

client.js:29 [Client] TypeError: Cannot read properties of undefined (reading 'digest')
    at tG (client.js:70:10491)
    at nV (client.js:70:10663)
    at xd.init (client.js:342:254229)
    at client.js:345:2453

Using image id f524a821e9bd (:latest tag right now) and Google Chrome on Fedora Linux. Wiped browser cache after update.

12

Don’t use 0.0.0.0 use 127.0.0.1 or plain localhost

13

Ah, that works. Thanks a lot!

I stupidly read:

just anything other than localhost

as: “Do not use localhost” :face_with_peeking_eye:

Mostly only used 0.0.0.0, because thats what was suggested by the startup output

2025/11/06 12:18:23 SilverBullet is now running: http://0.0.0.0:3000

But I guess thats just the bind address :slight_smile:

14

Yes indeed, when run in docker it’s the bind address.

15

I’m experiencing this issue after updating to v2.2. I’m running SilverBullet with Docker on a Linux machine in my intranet (accessing via HTTP bind address). After troubleshooting, my temporary workaround is to roll back to v2.1.4, which works perfectly.
Here are the specific errors I encountered:
Blank page after login showing {“redirect”:“/”,“status”:“ok”}
Docker logs showing: Error verifying JWT on /favicon.png: token signature is invalid
Unauthorized access errors to /.fs/Library/Std/Config.md and other internal files

These issues are a bit beyond my knowledge level to debug properly, so I’ll stick with v2.1.4 until I figure out the proper configuration for v2.2 or higher.
Has anyone successfully got v2.2 working with Docker and HTTP (no HTTPS)?