Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unknown error when using mail function #4

Closed
Jeltel opened this issue Aug 16, 2019 · 11 comments
Closed

Unknown error when using mail function #4

Jeltel opened this issue Aug 16, 2019 · 11 comments

Comments

@Jeltel
Copy link

Jeltel commented Aug 16, 2019

Problem/Motivation

I'm trying to invite new users and also adding users to my orginisation. Both function require a mail to be sent.
So i've configured a smtp server (which is operational), but I can't test the integration.

Expected behavior

I expect the bitwarden application to sent a mail to the email address entered.

Actual behavior

No mail is sent (nothing seen in the smpt server) and the interface returns an Unknown Error.
It does note the mail address as invited.
In the log it says the following when inviting a user:

[2019-08-16 22:00:54][rocket::rocket][INFO] POST /admin/invite/ application/json:
[2019-08-16 22:00:54][_][INFO] Matched: POST /admin/invite (invite_user)
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Io(Custom { kind: Other, error: StringError("failed to lookup address information: Temporary failure in name resolution") })', src/libcore/result.rs:999:5

And when (re-)inviting a user to the organisation:

[2019-08-16 22:10:00][_][INFO] Matched: POST /api/organizations/<org_id>/users/<user_org>/reinvite (reinvite_user)
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Io(Custom { kind: Other, error: StringError("failed to lookup address information: Temporary failure in name resolution") })', src/libcore/result.rs:999:5

So same error. Some name resolution thing. When it is strange that other application (my mail server itself, can sent mails via the same smtp

Steps to reproduce

Adding a smtp server configuration the bitwarden vault and then inviting a user.

@addons-assistant
Copy link

👋 Thanks for opening your first issue here! If you're reporting a 🐛 bug, please make sure you include steps to reproduce it. Also, logs, error messages and information about your hardware might be usefull.

@Jeltel
Copy link
Author

Jeltel commented Aug 16, 2019

Or is this just a strange way of saying my smtp configuration is wrong?

@sinclairpaul
Copy link
Member

What did you specify for the SMTP server, can it be resolved by the addon?

@Jeltel
Copy link
Author

Jeltel commented Aug 17, 2019

SMTP.sendgrid.net

And how can I check if the add-on can resolve that?

@frenck
Copy link
Member

frenck commented Aug 17, 2019

"Temporary failure in name resolution" looks like a DNS issue to me...

@Jeltel
Copy link
Author

Jeltel commented Aug 17, 2019

The machine on which hassio and bitwarden are running can ping SMTP.sendgrid.net.

But I also cannot see any icons. So maybe there is some nameresolving issue.

@frenck
Copy link
Member

frenck commented Aug 17, 2019

The host is not relevant in this case. The error message is clear, it cannot resolve the given fqdn.

@Jeltel
Copy link
Author

Jeltel commented Aug 17, 2019

Ok, how can I check from inside bitwarden. Can I use docker-exec with ping?

Edit: hmm ping is not there inside the bitwarden docker.
So how can I check if the add-on can reach my SMTP server?

@Jeltel
Copy link
Author

Jeltel commented Aug 17, 2019

Ok, changed to an internal smtp relay server and now it does work. Strange. Because other devices on my network can connect directly to sendgrid.

Then the issue is the generated error. It shouldn't say unknown error in the interface.

@frenck
Copy link
Member

frenck commented Aug 17, 2019

That is not in control of this add-on, add-ons wrap existing software.

@frenck frenck closed this as completed Aug 17, 2019
@addons-assistant
Copy link

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.

@addons-assistant addons-assistant bot locked as resolved and limited conversation to collaborators Sep 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants