Using a fresh Telegram token and a self-signed cert made with OpenSSL, my server returns an unknown certificate error when imitating Telegram. How can I fix this?
Example:
openssl t_client -connect myserver:443 -CAfile mycert.pem
I experienced a similar issue when trying to use a self-signed certificate with a messaging API. The key point is that self-signed certificates usually require additional verification that trusted certificate authorities automatically perform. My approach was to double-check that the certificate chain was complete and correctly referenced in the server configuration. In my case, switching to a certificate from a well-known CA resolved the issue. However, if a self-signed solution is necessary, one workaround was to manually add the certificate to the client’s trust store and configure the API webhook settings accordingly. It might take some extra adjustments to get your setup working.