mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-02-05 00:29:40 +03:00
[Bug] v1.32.5 resend org invitation: An error has occurred. Handlebars #2106
Reference in New Issue
Block a user
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?
Originally created by @jb2barrels on GitHub (Dec 10, 2024).
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden: DOMAIN, USER_ATTACHMENT_LIMIT, ORG_ATTACHMENT_LIMIT, INCOMPLETE_2FA_TIME_LIMIT, SIGNUPS_ALLOWED, SIGNUPS_VERIFY, SIGNUPS_DOMAINS_WHITELIST, ORG_CREATION_USERS, EMERGENCY_ACCESS_ALLOWED, EMAIL_CHANGE_ALLOWED, PASSWORD_HINTS_ALLOWED, ADMIN_TOKEN, INVITATION_ORG_NAME, RELOAD_TEMPLATES, ADMIN_SESSION_LIFETIME, YUBICO_CLIENT_ID, YUBICO_SECRET_KEY, SMTP_HOST, SMTP_SECURITY, SMTP_PORT, SMTP_FROM, SMTP_FROM_NAME, SMTP_USERNAME, SMTP_PASSWORD, SMTP_TIMEOUT
Vaultwarden Build Version
v1.32.5
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
Nginx Proxy Manager & Cloudflare
Host/Server Operating System
Linux
Operating System Version
Debian 12
Clients
Web Vault
Client Version
No response
Steps To Reproduce
Expected Result
Invite is resent instead of error
Actual Result
Error is received
Logs
No response
Screenshots or Videos
No response
Additional Context
No response
@BlackDex commented on GitHub (Dec 10, 2024):
It might help to know what the actual error is.
@jb2barrels commented on GitHub (Dec 10, 2024):
The error is 'An error has occurred. Handlebars'

@BlackDex commented on GitHub (Dec 10, 2024):
What do the Vaultwarden logs report?
@stefan0xC commented on GitHub (Dec 10, 2024):
It sounds like you might be using outdated handlebar templates?
@BlackDex commented on GitHub (Dec 10, 2024):
That is what I think too, but would like to see the actual error 😄
@jb2barrels commented on GitHub (Dec 10, 2024):
Thanks, I think that may be the issue. I will try modifying the custom template I am using and report back if resolved.