mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 09:46:00 +03:00
[GH-ISSUE #2021] Unclear Error on saving SMTP config #1127
Labels
No 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
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#1127
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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 @victorshx on GitHub (Oct 4, 2021).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2021
Subject of the issue
I'm unable to save SMTP config, which is required for sending registration emails.
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden: DOMAIN, SIGNUPS_ALLOWED, ADMIN_TOKEN
Steps to reproduce
Expected behaviour
Config should be saved successfully
Actual behaviour
Troubleshooting data
@BlackDex commented on GitHub (Oct 4, 2021):
What do the logs say around the time you tried to save the config?
@victorshx commented on GitHub (Oct 4, 2021):
@BlackDex Where do I check the logs?
@BlackDex commented on GitHub (Oct 4, 2021):
Either in your data folder as vaultwarden.log, or use
docker logs -f vaultwardenor whatever you named your container.@victorshx commented on GitHub (Oct 4, 2021):
Thanks for the prompt reply! I managed to pinpoint the issue by reading the logs.
@BlackDex commented on GitHub (Oct 4, 2021):
@victorshx could you tell us a bit what the issue was?
I would like to see if we can improve upon the error message shown in the web interface.
@victorshx commented on GitHub (Oct 5, 2021):
@BlackDex Firstly, I think the error message in the web interface can be more verbose since logs have already shown which field is missing.
Secondly, failing to send due to TLS enabled will show this error in the web interface.
@BlackDex commented on GitHub (Oct 5, 2021):
Thanks, i have found the issue i think. Now i need to find a way to solve it ;)