I have searched the existing issues and discussions
I have read the documentation
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Vaultwarden version: v1.34.1
Web-vault version: v2025.5.0
OS/Arch: linux/x86_64
Running within a container: true (Base: Debian)
Database type: SQLite
Database version: 3.49.1
Uses config.json: false
Uses a reverse proxy: true
IP Header check: true (X-Real-IP)
Internet access: true
Internet access via a proxy: false
DNS Check: true
TZ environment: Europe/Brussels
Browser/Server Time Check: true
Server/NTP Time Check: true
Domain Configuration Check: true
HTTPS Check: true
Websocket Check: true
HTTP Response Checks: false
Config & Details (Generated via diagnostics page)
Show Config & Details
Failed HTTP Checks:
API calls:Header:'x-xss-protection'does not contain '0'2FA Connector calls:Header:'x-xss-protection'does not contain '0'Header:'x-frame-options'is present while it should not
<!-- gh-comment-id:3117063892 -->
@BlackDex commented on GitHub (Jul 25, 2025):
<img width="438" height="152" alt="Image" src="https://github.com/user-attachments/assets/1f53c04f-5a02-4cfc-9fee-9e59563503e6" />
You checked the boxes but did not search!
Please search again!
Sorry folks. I did review the open incidents and there were none. So, my assumption was that this was something new. From reading the provided links, it seems there is a fix, but nothing has been pushed to the stable release, is that correct?
<!-- gh-comment-id:3118091342 -->
@mrjlturner commented on GitHub (Jul 25, 2025):
Sorry folks. I did review the open incidents and there were none. So, my assumption was that this was something new. From reading the provided links, it seems there is a fix, but nothing has been pushed to the stable release, is that correct?
Sorry folks. I did review the open incidents and there were none. So, my assumption was that this was something new. From reading the provided links, it seems there is a fix, but nothing has been pushed to the stable release, is that correct?
Yes.
It is in :testing
<!-- gh-comment-id:3118774955 -->
@zzahkaboom24 commented on GitHub (Jul 25, 2025):
> Sorry folks. I did review the open incidents and there were none. So, my assumption was that this was something new. From reading the provided links, it seems there is a fix, but nothing has been pushed to the stable release, is that correct?
Yes.
It is in `:testing`
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 @Jordi-Jaspers on GitHub (Jul 25, 2025).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6091
Prerequisites
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Failed HTTP Checks:
Config:
Vaultwarden Build Version
1.34.1
Deployment method
Official Container Image
Custom deployment method
docker compose
Reverse Proxy
Traefik 3.4.4
Host/Server Operating System
Linux
Operating System Version
Debian GNU/Linux 12 (bookworm) x86_64
Clients
Web Vault
Client Version
No response
Steps To Reproduce
Expected Result
There should be a delete button somewhere? Can't seem to find it.
Actual Result
No button found
Logs
Screenshots or Videos
No response
Additional Context
No response
@BlackDex commented on GitHub (Jul 25, 2025):
Please search again!
@mrjlturner commented on GitHub (Jul 25, 2025):
Sorry folks. I did review the open incidents and there were none. So, my assumption was that this was something new. From reading the provided links, it seems there is a fix, but nothing has been pushed to the stable release, is that correct?
@zzahkaboom24 commented on GitHub (Jul 25, 2025):
Yes.
It is in
:testing