starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-02-05 00:29:40 +03:00
Code Issues 32 Packages Projects Releases 10 Wiki Activity

Emergency access sends a lot of emails when the wait time period is reached #1420

New Issue
Closed
opened 2026-02-05 00:54:02 +03:00 by OVERLORD · 2 comments
OVERLORD commented 2026-02-05 00:54:02 +03:00
Owner
Copy Link

Originally created by @spctechdev on GitHub (Dec 4, 2022).

Subject of the issue

Vaultwarden sends too much emails when the emergency access wait time lapses or grantor approve the request

Deployment environment

  • Vaultwarden version: v1.26.0

  • Web-vault version: v2022.10.0

  • Running within Docker: true (Base: Debian)

  • Environment settings overridden: 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

  • Time Check: true

  • Domain Configuration Check: true

  • HTTPS Check: true

  • Database type: SQLite

  • Database version: 3.35.4

  • Other relevant details:

Steps to reproduce

Make an emergency request for another account and wait the time the grantor setted.

Expected behaviour

Only one or some emails to inform that the emergency access is pending

Actual behaviour

The grantor receives a lot of emails when the emergency wait time is reached

Troubleshooting data

mails

Originally created by @spctechdev on GitHub (Dec 4, 2022). <!-- # ### NOTE: Please update to the latest version of vaultwarden before reporting an issue! This saves you and us a lot of time and troubleshooting. See: * https://github.com/dani-garcia/vaultwarden/issues/1180 * https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image # ### --> <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them. Remember to hide/redact personal or confidential information, such as passwords, IP addresses, and DNS names as appropriate. --> ### Subject of the issue Vaultwarden sends too much emails when the emergency access wait time lapses or grantor approve the request ### Deployment environment <!-- ========================================================================================= Preferably, use the `Generate Support String` button on the admin page's Diagnostics tab. That will auto-generate most of the info requested in this section. ========================================================================================= --> <!-- The version number, obtained from the logs (at startup) or the admin diagnostics page --> <!-- This is NOT the version number shown on the web vault, which is versioned separately from vaultwarden --> <!-- Remember to check if your issue exists on the latest version first! --> <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Vaultwarden version: v1.26.0 * Web-vault version: v2022.10.0 * Running within Docker: true (Base: Debian) * Environment settings overridden: 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 * Time Check: true * Domain Configuration Check: true * HTTPS Check: true * Database type: SQLite * Database version: 3.35.4 * Other relevant details: ### Steps to reproduce Make an emergency request for another account and wait the time the grantor setted. ### Expected behaviour Only one or some emails to inform that the emergency access is pending ### Actual behaviour The grantor receives a lot of emails when the emergency wait time is reached ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data --> ![mails](https://user-images.githubusercontent.com/111750395/205474020-7e7c49cd-a670-4579-904b-4b7ef619d5f1.png)
OVERLORD added the enhancementbug labels 2026-02-05 00:54:02 +03:00
OVERLORD commented 2026-02-05 00:54:04 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Dec 4, 2022):

Probably fixed by #2936 .

In the mean time you could change the cron schedule time for both emergency access jobs to the new default i set in that PR.

4aa6dd22bb/.env.template (L121...L127)

@BlackDex commented on GitHub (Dec 4, 2022): Probably fixed by #2936 . In the mean time you could change the cron schedule time for both emergency access jobs to the new default i set in that PR. https://github.com/dani-garcia/vaultwarden/blob/4aa6dd22bbe853542c2396821648f369d07bb951/.env.template#L121...L127
OVERLORD commented 2026-02-05 00:54:07 +03:00
Author
Owner
Copy Link

@tessus commented on GitHub (Dec 5, 2022):

@BlackDex the PR was approved by Dani. Doesn't that mean you can merge it to main?
Once again. just wondering. It always depends on how a project is run.

@tessus commented on GitHub (Dec 5, 2022): @BlackDex the PR was approved by Dani. Doesn't that mean you can merge it to main? Once again. just wondering. It always depends on how a project is run.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
Mirrored from GitHub Pull Request
 question
troubleshooting
wontfix
No Label bug enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#1420
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?