Unable to get local issuer certificate on Telgram Notification #3893

Closed
opened 2026-02-28 03:44:23 -05:00 by deekerman · 1 comment
Owner

Originally created by @gobbe87 on GitHub (Jan 13, 2025).

⚠️ Please verify that this question has NOT been raised before.

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

I'm trying to setup Telegram notification on my new Uptime Kuma environment. I defined all parameters and retrieved ChatID correctly but when I make e test I received the error: "unable to get local issuer certificate"

Screenshot 2025-01-13 145959

📝 Error Message(s) or Log

unable to get local issuer certificate

🐻 Uptime-Kuma Version

1.23.16

💻 Operating System and Arch

ubuntu2~22.04.1 on WSL

🌐 Browser

Google Chrome 131.0.6778.265

🖥️ Deployment Environment

  • Runtime: Docker version 24.0.7, build 24.0.7-0ubuntu2~22.04.1
  • Database:
  • Filesystem used to store the database on: Windows
  • number of monitors: 20
Originally created by @gobbe87 on GitHub (Jan 13, 2025). ### ⚠️ Please verify that this question has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### 📝 Describe your problem I'm trying to setup Telegram notification on my new Uptime Kuma environment. I defined all parameters and retrieved ChatID correctly but when I make e test I received the error: "_unable to get local issuer certificate_" ![Screenshot 2025-01-13 145959](https://github.com/user-attachments/assets/f9e76ece-2b0b-48bf-bf48-0f5120c1984e) ### 📝 Error Message(s) or Log unable to get local issuer certificate ### 🐻 Uptime-Kuma Version 1.23.16 ### 💻 Operating System and Arch ubuntu2~22.04.1 on WSL ### 🌐 Browser Google Chrome 131.0.6778.265 ### 🖥️ Deployment Environment - Runtime: Docker version 24.0.7, build 24.0.7-0ubuntu2~22.04.1 - Database: - Filesystem used to store the database on: Windows - number of monitors: 20
deekerman 2026-02-28 03:44:23 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Mar 18, 2025):

We are clearing up our old help-issues and your issue has been open for 60 days with no activity.
If no comment is made and the stale label is not removed, this issue will be closed in 7 days.

@github-actions[bot] commented on GitHub (Mar 18, 2025): We are clearing up our old `help`-issues and your issue has been open for 60 days with no activity. If no comment is made and the stale label is not removed, this issue will be closed in 7 days.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#3893
No description provided.