github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-06 03:27:53 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #34] Bug: Certificate error on SMTP connection #5860

New Issue
Closed
opened 2026-04-20 16:15:06 -05:00 by GiteaMirror · 8 comments
GiteaMirror commented 2026-04-20 16:15:06 -05:00
Owner
Copy Link

Originally created by @mtettke123 on GitHub (Jul 11, 2022).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/34

Hi out there,

I'm trying to get Vikunja to talk to my SMTP server. My server has a certificate with a public name, but I connect via a private connection (VM to VM), not via public net.

Although I've set I
VIKUNJA_MAILER_SKIPTLSVERIFY: "true"
get the error message:
mail/func1 1d3 Error during connect to smtp server: %s x509: certificate is valid for <external DNS name>, not <internal DNS name>

It doesn't matter if I use the internal DNS name or the IP address of the server, with the latter one I get:
mail/func1 1da Error during connect to smtp server: %s x509: cannot validate certificate for 10.100.0.21 because it doesn't contain any IP SANs

This seems to be a bug or am I missing something?

Originally created by @mtettke123 on GitHub (Jul 11, 2022). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/34 Hi out there, I'm trying to get Vikunja to talk to my SMTP server. My server has a certificate with a public name, but I connect via a private connection (VM to VM), not via public net. Although I've set I `VIKUNJA_MAILER_SKIPTLSVERIFY: "true"` get the error message: `mail/func1 1d3 Error during connect to smtp server: %s x509: certificate is valid for <external DNS name>, not <internal DNS name>` It doesn't matter if I use the internal DNS name or the IP address of the server, with the latter one I get: `mail/func1 1da Error during connect to smtp server: %s x509: cannot validate certificate for 10.100.0.21 because it doesn't contain any IP SANs` This seems to be a bug or am I missing something?
GiteaMirror added the bug label 2026-04-20 16:15:07 -05:00
GiteaMirror commented 2026-04-20 16:15:09 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jul 11, 2022):

Should be fixed in 5743a4afe5 - please try in ~30 min with the next unstable build.

<!-- gh-comment-id:1180461008 --> @kolaente commented on GitHub (Jul 11, 2022): Should be fixed in 5743a4afe51de221beeeabe66552ae4d92eed1a6 - please try in ~30 min with the next unstable build.
GiteaMirror commented 2026-04-20 16:15:11 -05:00
Author
Owner
Copy Link

@mtettke123 commented on GitHub (Jul 11, 2022):

Can confirm SKIPTLSVERIFY is working now. Thank you!
Buuuut:
How can I send Emails without auth? Now I get
mail/func1 1d2 Error during connect to smtp server: %s SMTP AUTH failed: 535 Incorrect authentication data
although I don't need auth.

Setting VIKUNJA_MAILER_USERNAME to "" does not help. How can I set up mailing WITHOUT auth?

<!-- gh-comment-id:1180853565 --> @mtettke123 commented on GitHub (Jul 11, 2022): Can confirm SKIPTLSVERIFY is working now. Thank you! Buuuut: How can I send Emails without auth? Now I get `mail/func1 1d2 Error during connect to smtp server: %s SMTP AUTH failed: 535 Incorrect authentication data` although I don't need auth. Setting VIKUNJA_MAILER_USERNAME to "" does not help. How can I set up mailing WITHOUT auth?
GiteaMirror commented 2026-04-20 16:15:12 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jul 12, 2022):

So it looks like the default username Vikunja used to connect to a mail server was user. I don't know why I set it to that. Changed in 4bb77b5539 so that it should accept an empty user by default or when explicitly configured. Can you try again with the next unstable build?

<!-- gh-comment-id:1181557216 --> @kolaente commented on GitHub (Jul 12, 2022): So it looks like the default username Vikunja used to connect to a mail server was `user`. I don't know why I set it to that. Changed in 4bb77b5539ccf9e035ef2b58bfa93d0eb5feb37e so that it should accept an empty user by default or when explicitly configured. Can you try again with the next unstable build?
GiteaMirror commented 2026-04-20 16:15:12 -05:00
Author
Owner
Copy Link

@mtettke123 commented on GitHub (Jul 12, 2022):

Still doesnt't work, same error. It tries to authenticate. Doesn't matter if I set VIKUNJA_MAILER_USERNAME: "" or not.

Mailserver says:
2022-07-12 13:06:09 fixed_plain authenticator failed for (f93e466b6eb2) [10.100.0.145]: 535 Incorrect authentication data

<!-- gh-comment-id:1181627930 --> @mtettke123 commented on GitHub (Jul 12, 2022): Still doesnt't work, same error. It tries to authenticate. Doesn't matter if I set VIKUNJA_MAILER_USERNAME: "" or not. Mailserver says: `2022-07-12 13:06:09 fixed_plain authenticator failed for (f93e466b6eb2) [10.100.0.145]: 535 Incorrect authentication data`
GiteaMirror commented 2026-04-20 16:15:13 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jul 12, 2022):

New attempt to fix in c906fc2b07 - please try again with the next unstable build in ~30 min.

(Biggest problem is I can't really test this)

<!-- gh-comment-id:1181783415 --> @kolaente commented on GitHub (Jul 12, 2022): New attempt to fix in https://github.com/go-vikunja/api/commit/c906fc2b07624747af1d7819e0fc270fc7b4c070 - please try again with the next unstable build in ~30 min. (Biggest problem is I can't really test this)
GiteaMirror commented 2026-04-20 16:15:14 -05:00
Author
Owner
Copy Link

@mtettke123 commented on GitHub (Jul 12, 2022):

still the same :-(

would it help you if I would create a VM for you to test?

<!-- gh-comment-id:1181924969 --> @mtettke123 commented on GitHub (Jul 12, 2022): still the same :-( would it help you if I would create a VM for you to test?
GiteaMirror commented 2026-04-20 16:15:15 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jul 12, 2022):

Sure.

<!-- gh-comment-id:1181942272 --> @kolaente commented on GitHub (Jul 12, 2022): Sure.
GiteaMirror commented 2026-04-20 16:15:17 -05:00
Author
Owner
Copy Link

@mtettke123 commented on GitHub (Jul 12, 2022):

You've got mail.

<!-- gh-comment-id:1182006891 --> @mtettke123 commented on GitHub (Jul 12, 2022): You've got mail.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#5860
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?