[GH-ISSUE #1219] Expired Certificates for Debian Repository #861

Closed
opened 2026-05-07 00:28:14 +02:00 by BreizhHardware · 1 comment

Originally created by @alexfornuto on GitHub (Nov 11, 2024).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1219

🐞 Describe the bug
The TLS certificate(s) for heckel.io and the archive subdomain expired today, preventing secure access to the packages.

💻 Components impacted
New users installing, existing users updating

💡 Screenshots and/or logs

Err:7 https://archive.heckel.io/apt debian InRelease
  Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate.  Could not handshake: Error in the certificate verification. [IP: 46.163.76.87 443]

image

🔮 Additional context
Should be as easy as a single certbot command to resolve, depending on your hosting infrastructure.

Originally created by @alexfornuto on GitHub (Nov 11, 2024). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1219 :lady_beetle: **Describe the bug** The TLS certificate(s) for heckel.io and the archive subdomain expired today, preventing secure access to the packages. :computer: **Components impacted** New users installing, existing users updating :bulb: **Screenshots and/or logs** ```apt Err:7 https://archive.heckel.io/apt debian InRelease Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the certificate verification. [IP: 46.163.76.87 443] ``` ![image](https://github.com/user-attachments/assets/58281cc9-a558-456a-9a95-f6a61bf56a17) :crystal_ball: **Additional context** Should be as easy as a single `certbot` command to resolve, depending on your hosting infrastructure.
BreizhHardware 2026-05-07 00:28:14 +02:00
  • closed this issue
  • added the
    🪲 bug
    label
Author
Owner

@alexfornuto commented on GitHub (Nov 12, 2024):

Looks like it's been updated.

<!-- gh-comment-id:2469571768 --> @alexfornuto commented on GitHub (Nov 12, 2024): Looks like it's been updated.
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/ntfy#861
No description provided.