404 on latest release

[jnobbe]

On the latest release I'm encountering a simple 404 message instead of anything loading. I checked the logs and I'm not seeing anything there. I also look at Traefik, nothing there aside from the 404's.

The network logs show .config, Schema.md, Config.md, and CONFIG.md are not found both from client.js an service worker.js as initiators.

When I switch tags to 4.2.1 things start working again. I just tried going back to v2 and immediately encountered this issue again. There isn't anything crazy about the compose file.

[zefhemel]

To be clear, when you say release you mean the :v2 docker tag right? (Release tag is :latest)

[jnobbe]

Yes, that's correct, Zef. I've been using v2 and updated going into the weekend. I think I noticed on Saturday.

[zefhemel]

Does the same thing happen in a different browser, after clearing the cache. Incognito mode? What browser are you using?

I run on :v2 and don't see this.

[jnobbe]

Yes, it's also happening on Librewolf. My daily driver is Vivaldi. I cleared cookies and cache to no avail. Turning off ad blockers for good measure also doesn't make any difference.

[zefhemel]

I just checked what changed since the last release and main on the server end and it's nothing except some authentication cookie stuff. Can you determine what version of the image you were testing? What version is reported by Client: Version?

I assume the silverbullet server itself doesn't report the 404s (it doesn't by default). But Traefik does? So you see requests being make to e.g. /.config and it 404'ing? Could you set the SB_HTTP_LOGGING=1 for SilverBullet and see if you can replicate this and if those requests are indeed served as 404s from the SilverBullet server end?

[jnobbe]

I just flip-flopped between 2.4.1 and v2 again and added SB_HTTP_LOGGING=1. I initially received the 404 page again. However, I use Authelia in front of a lot of my services -- so, as I was going to check out logs with Portainer I had to authenticate. I refreshed Silverbullet and lo and behold it loaded up. This wasn't the experience I've had over the last few days though. I know I was authenticated with Authelia during those incidents. I don't have Authelia or Traefik set to update to latest so I'm not sure what would have been different this past weekend. Normally, I can go through the authentication flow without issue prior to accessing SB. I'm thinking that the issue was with Authelia based on what I'm seeing but it's really a mystery to me, I checked the Authelia logs over the weekend and nothing stood out at the time.

Client: Version now reports 2.4.1-71-g4c169371 using the v2 tag.

[dukemiller]

I had a similar troubleshooting experience with this latest (previous?) version. Yesterday my self-hosted instance using latest :v2 (24915390964c) was returning 404s + a blank page. When attempting to hard refresh and view on separate browsers, I noticed the container was restarting (no SB_HTTP_LOGGING=1 unfortunately)

2026/02/02 17:06:27 Local shell command execution enabled for ALL commands.
2026/02/02 17:06:27 SilverBullet is now running: http://0.0.0.0:3000
2026/02/02 17:08:56 Local shell command execution enabled for ALL commands.
2026/02/02 17:08:56 SilverBullet is now running: http://0.0.0.0:3000

It reset again this morning (updated via watchtower, 54bea074db69 was pushed), and now all behavior with the application is fine.