I opened up the F12 and forced a refresh with "Disable Cache" enabled, and that seems to have solved the problem. Something must have been cached.
All is OK.
<!-- gh-comment-id:4442485629 -->
@mwhouser commented on GitHub (May 13, 2026):
False alarm.
I opened up the F12 and forced a refresh with "Disable Cache" enabled, and that seems to have solved the problem. Something must have been cached.
All is OK.
Besides that, this feature is fully client-side and has nothing to do with the server side, which is what Vaultwarden is.
<!-- gh-comment-id:4442661034 -->
@BlackDex commented on GitHub (May 13, 2026):
Besides that, this feature is fully client-side and has nothing to do with the server side, which is what Vaultwarden is.
Uhm, right there in the Support String: Web-vault version: v2026.4.1
I understand that it may be client side, but the web vault (that I was using) is provided by the Vaultwarden docker image.
So it's not like I was using someone else's front-end (like the BitWarden tools are).
<!-- gh-comment-id:4443210362 -->
@mwhouser commented on GitHub (May 13, 2026):
@BlackDex
Uhm, right there in the Support String: `Web-vault version: v2026.4.1`
I understand that it may be client side, but the web vault (that I was using) is provided by the Vaultwarden docker image.
So it's not like I was using someone else's front-end (like the BitWarden tools are).
<!-- gh-comment-id:4443247135 -->
@BlackDex commented on GitHub (May 13, 2026):
> [@BlackDex](https://github.com/BlackDex)
>
> Uhm, right there in the Support String: `Web-vault version: v2026.4.1`
>
> I understand that it may be client side, but the web vault (that I was using) is provided by the Vaultwarden docker image.
>
> So it's not like I was using someone else's front-end (like the BitWarden tools are).
Yes you are, the web-vault is not developed or maintained by Vaultwarden.
Also read: https://github.com/dani-garcia/vaultwarden/wiki/FAQs#i-have-a-feature-request-for-the-web-vault-or-any-other-client
That's specifically talking about feature requests. This was a bug report.
<!-- gh-comment-id:4443323402 -->
@mwhouser commented on GitHub (May 13, 2026):
> the web-vault is not developed or maintained by Vaultwarden.
Where is this documented?
From the web-vault, I did "Get Help" and it took me here.
> Also read: https://github.com/dani-garcia/vaultwarden/wiki/FAQs#i-have-a-feature-request-for-the-web-vault-or-any-other-client
That's specifically talking about feature requests. This was a bug report.
Just take my word for it. And multiple other reports regarding items like this, including the same about searching have been answered the same way.
<!-- gh-comment-id:4443681238 -->
@BlackDex commented on GitHub (May 13, 2026):
Just take my word for it. And multiple other reports regarding items like this, including the same about searching have been answered the same way.
I was under the (I guess wrong) impression that the web front-end was part of Vaultwarden.
<!-- gh-comment-id:4443813793 -->
@mwhouser commented on GitHub (May 13, 2026):
Then I would *highly recommend* documenting it somewhere front-and-centre.
1. The web-vault, that's packaged with Vaultwarden in the official docker image,
2. Has "Vaultwarden" splattered all over it, and
3. The "Get Help" menu takes you **to this Github repo**.
4. Finally, the Vaultwarden Wiki explicitly says "Vaultwarden implements [...] Web interface": https://github.com/dani-garcia/vaultwarden/wiki#supported-features
I was under the (I guess wrong) impression that the web front-end was part of Vaultwarden.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @mwhouser on GitHub (May 13, 2026).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/7213
Prerequisites
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Environment settings which are overridden: DOMAIN, ADMIN_TOKEN
Config:
Vaultwarden Build Version
1.36.0
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
Nginx Proxy Manager v2.13.5
Host/Server Operating System
Linux
Operating System Version
Ubuntu 24.04
Clients
Web Vault
Client Version
2026.4.1
Steps To Reproduce
Expected Result
The results should show vault entries that match my search term
Actual Result
The search is wrong and/or empty (usually empty).
Logs
Screenshots or Videos
No response
Additional Context
I upgraded from 2026.1.1 to 2026.4.1 (updated the docker image). I'm not sure the server version that was installed previously.
Search was working fine with 2026.1.1, but now with 2026.4.1, search is just broken.
Another example:
It should show 4 results that includes "pizza" in the name.
@mwhouser commented on GitHub (May 13, 2026):
False alarm.
I opened up the F12 and forced a refresh with "Disable Cache" enabled, and that seems to have solved the problem. Something must have been cached.
All is OK.
@BlackDex commented on GitHub (May 13, 2026):
Besides that, this feature is fully client-side and has nothing to do with the server side, which is what Vaultwarden is.
@mwhouser commented on GitHub (May 13, 2026):
@BlackDex
Uhm, right there in the Support String:
Web-vault version: v2026.4.1I understand that it may be client side, but the web vault (that I was using) is provided by the Vaultwarden docker image.
So it's not like I was using someone else's front-end (like the BitWarden tools are).
@BlackDex commented on GitHub (May 13, 2026):
Yes you are, the web-vault is not developed or maintained by Vaultwarden.
Also read: https://github.com/dani-garcia/vaultwarden/wiki/FAQs#i-have-a-feature-request-for-the-web-vault-or-any-other-client
@mwhouser commented on GitHub (May 13, 2026):
Where is this documented?
From the web-vault, I did "Get Help" and it took me here.
That's specifically talking about feature requests. This was a bug report.
@BlackDex commented on GitHub (May 13, 2026):
Just take my word for it. And multiple other reports regarding items like this, including the same about searching have been answered the same way.
@mwhouser commented on GitHub (May 13, 2026):
Then I would highly recommend documenting it somewhere front-and-centre.
I was under the (I guess wrong) impression that the web front-end was part of Vaultwarden.