Closed adriamontoto closed 2 months ago
@adriiamontoto Thanks for the suggestion. I'm not sure how to recognize self-signed certificates without turning off other also useful checking in Go (and without re-implementing the HTTP stack)---I guess I need help. In the meanwhile, there are two possible ways to solve this, and the first one is highly recommended:
/etc/ssl/certs/ca-certificates.crt
.)Thank you for your quick response, I would go with option number 2!
@adriiamontoto Let me know if you need help, and I still strongly recommend option 1. :-)
@adriiamontoto I am closing this issue because there's nothing for me to do now. Please re-open it if you have other suggestions.
Issue Description When attempting to send HTTP(S) requests to Uptime Kuma, users may encounter the error message: "😞 Failed to send HTTP(S) request to Uptime Kuma: tls: failed to verify certificate: x509: certificate signed by unknown authority." This issue arises due to the certificate verification process during HTTPS communication.
Proposal I suggest implementing a new flag or mechanism within Uptime Kuma that allows users to bypass the "certificate signed by unknown authority" error. This would provide flexibility to use self signed certificates for developing/home server environments.
Examples: In uptime kuma there is an option to ignore TLS/SSL error for HTTPS websites.![image](https://github.com/favonia/cloudflare-ddns/assets/75563346/6cdc2c28-5e00-4935-ba0d-39dc28db13bd)