this post was submitted on 29 Nov 2025
8 points (90.0% liked)
Joplin
919 readers
1 users here now
Official community of Joplin - the secure open-source note-taking app.
Capture your thoughts and securely access them from any device.
- ๐ Website
- ๐ฌ Forums
- ๐ Support the developer
Features:
- ๐ sync via Joplin Cloud, NextCloud, Dropbox, OneDrive, Syncthing, WebDAV
- ๐ web clipper extension
- ๐ก๏ธ end-to-end encryption
- โ๏ธ Markdown support
- โ built-in todo manager
- ๐ฑ runs on every desktop and mobile OS
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I don't know much about using the Synology, can you do the normal debugging things like
docker exec -it joplincontainer shto get a shell?Are the security settings allowing outbound connections? Can the Joplin container resolve the DNS? I'm assuming you're using an externally provided SMTP server, or is it hosted on the NAS/on your LAN too?
And have you tried those exact connection details on a different device from your house, or ideally from the NAS (with the exec sh/bash command from earlier)?
openssl s_client -connect smtp.provider.net:465is a handy command for testing the low level connection; you should see some SSL connection debug followed by something like220 s1.provider.net ESMTP Postfix.Thank you.
I tried these things. I can get a shell using the command you gave me.
Bute the second test withj openssl does not work within the container shell because of the missing openssl command.
But it worked directly on the NAS. i got
220 mxe83f.netcup.net ESMTP Postfix (Debian/GNU)as response from the server