Notifications health check remains unavailable after certificate renewal
Timeline correction: this ticket was created October 21 for an already ongoing outage. Its outage interval now follows original automatic incident d75a0159: September 26 02:31:56 to October 21 15:18:29 (Asia/Shanghai). Ticket creation and investigation updates retain their original timestamps. Certificate mismatch was confirmed October 21; earlier outage checks did not preserve enough evidence to attribute every prior failure to that same cause.
- Incident ID
- #79f29a1a
- Impact
- major
- Components
- notify
Updates
-
investigating Oct 21, 2026, 3:15 PM GMT+08:00
Investigation started October 21. Hub is currently operational and its renewed certificate passes TLS validation. Notify health endpoint and certificate deployment are being checked. Existing automatic incident: d75a0159.
-
identified Oct 21, 2026, 3:19 PM GMT+08:00
Root cause confirmed: notify.internal.zhixing.center was served a certificate for *.zhixing.center, which does not cover the nested internal hostname. The notify application health endpoint itself remained healthy. The operator redeployed SSL; strict HTTPS validation now passes and the status poller reports notify and hub operational.
-
resolved Oct 21, 2026, 3:19 PM GMT+08:00
Resolved after operator SSL redeployment and successful strict HTTPS health checks. All components are operational; automatic notify incident d75a0159 also closed by the poller.
-
resolved Oct 21, 2026, 3:31 PM GMT+08:00
Timeline correction: this ticket was created October 21 for an already ongoing outage. Its outage interval now follows original automatic incident d75a0159: September 26 02:31:56 to October 21 15:18:29 (Asia/Shanghai). Ticket creation and investigation updates retain their original timestamps. Certificate mismatch was confirmed October 21; earlier outage checks did not preserve enough evidence to attribute every prior failure to that same cause.