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

E-Mail notification won't work #738

Closed
entonjackson opened this issue Apr 4, 2024 · 4 comments · Fixed by #737
Closed

E-Mail notification won't work #738

entonjackson opened this issue Apr 4, 2024 · 4 comments · Fixed by #737

Comments

@entonjackson
Copy link

First, thanks for this great piece of software.

At the moment I'm struggling setting up email notifications.

Testing e-mail notifications always results in an error:

image

[backend] thread 'tokio-runtime-worker' panicked at apps/backend/src/notification.rs:138:66: [backend] called Result::unwrap()on anErrvalue: InvalidInput [frontend] ClientError: GraphQL Error (Code: 500): {"response":{"error":"Service panicked","status":500,"headers":{}},"request":{"query":"mutation TestUserNotificationPlatforms {\n testUserNotificationPlatforms\n}"}} [frontend] at makeRequest (file:///home/ryot/node_modules/graphql-request/src/index.ts:426:11) [frontend] at processTicksAndRejections (node:internal/process/task_queues:95:5) [frontend] at Object.test (file:///home/ryot/build/server/index.js?t=1712132349000:7407:49) [frontend] at Object.callRouteActionRR (/home/ryot/node_modules/@remix-run/server-runtime/dist/data.js:35:16) [frontend] at callLoaderOrAction (/home/ryot/node_modules/@remix-run/router/router.ts:4043:16) [frontend] at submit (/home/ryot/node_modules/@remix-run/router/router.ts:3156:16) [frontend] at queryImpl (/home/ryot/node_modules/@remix-run/router/router.ts:3091:22) [frontend] at Object.queryRoute (/home/ryot/node_modules/@remix-run/router/router.ts:3041:18) [frontend] at handleDataRequestRR (/home/ryot/node_modules/@remix-run/server-runtime/dist/server.js:122:20) [frontend] at requestHandler (/home/ryot/node_modules/@remix-run/server-runtime/dist/server.js:94:18) { [frontend] response: { [frontend] error: 'Service panicked', [frontend] status: 500, [frontend] headers: Headers { [Symbol(map)]: [Object: null prototype] } [frontend] }, [frontend] request: { [frontend] query: 'mutation TestUserNotificationPlatforms {\n' + [frontend] ' testUserNotificationPlatforms\n' + [frontend] '}', [frontend] variables: undefined [frontend] } � [frontend] } [frontend] POST /settings/notifications?intent=test&_data=routes%2F_dashboard.settings.notifications 500 - - 325.488 ms

Variables should be setup correctly (probably redundant, but this shouldn't be an issue)

image

@IgnisDa
Copy link
Owner

IgnisDa commented Apr 4, 2024

Are you sure the variables are setup correctly? Do the same ones work for other services too?

@entonjackson
Copy link
Author

Yes they do. Usually you can specify whether to enable SSL or not. For example I have the diun docker container running with SSL enabled and Port 465. I don't know what's the default here, SSL on or off, but nevertheless the result was the same, for Port 465 and 587.

Here's the specification from mail.de.
image

Here's how I defined env vars for diun container:
image

@IgnisDa
Copy link
Owner

IgnisDa commented Apr 4, 2024

Alright I'll take a look.

@IgnisDa
Copy link
Owner

IgnisDa commented Apr 5, 2024

Please try trigerring a test notif with the latest version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants