-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
Open
Labels
A:notificationsIssues or PRs related to notificationsIssues or PRs related to notificationsbugSomething isn't workingSomething isn't working
Description
π I have found these related issues/pull requests
Unable to find any related issues/pull requests
π‘οΈ Security Policy
- I have read and agree to Uptime Kuma's Security Policy.
π Description
When trying to use an SMTP server that does not have any encryption protocols available, error occurs.
π Reproduction steps
Setup new Email/SMTP Notification.
- Host: Point to SMTP server that does not support TLS
- Port: 25
- Security: None / STARTTLS (25, 587)
π Expected behavior
Notification setup properly ignores TLS and/or does not look for it. Emails send through unencrypted SMTP server properly.
π Actual Behavior
App is using a setting that is expecting TLS, thus rejecting the notificaiotn setup.
Error Message: "Error upgrading connection with STARTTLS: 454 4.7.0 TLS not available due to local problem"
π» Uptime-Kuma Version
1.23.16
π» Operating System and Arch
Windows 11
π Browser
Brave (latest version)
π₯οΈ Deployment Environment
- Runtime Environment:
- Docker: Version
X.X.X
(BuildY.Y.Y
) - Docker Compose: Version
X.X.X
- Portainer (BE/CE): Version
X.X.X
(LTS: Yes/No) - MariaDB: Version
X.X.X
(LTS: Yes/No) - Node.js: Version
X.X.X
(LTS: Yes/No) - Kubernetes (K3S/K8S): Version
X.X.X
(LTS: Yes/No, via[method/tool]
)
- Docker: Version
- Database:
- SQLite: Embedded
- MariaDB: Embedded/External
- Database Storage:
- Filesystem:
- Linux: ext4/XFS/Btrfs/ZFS/F2FS
- macOS: APFS/ HFS+
- Windows: NTFS/ReFS
- Storage Medium: HDD/eMMC/SSD/NVMe
- Filesystem:
- Uptime Kuma Setup:
- Number of monitors:
X
- Number of monitors:
π Relevant log output
Metadata
Metadata
Assignees
Labels
A:notificationsIssues or PRs related to notificationsIssues or PRs related to notificationsbugSomething isn't workingSomething isn't working