Answer the question
In order to leave comments, you need to log in
Are Certbot certificates suitable for Telegram?
UPD: The
issue is resolved very simply:
has_custom_certificate is a flag for a self-signed certificate. Lets Encrypt doesn't need a Dog (@) icon.
The webhook is set even if you do not send a certificate, but simply set the webhook url with the https prefix
certbot --apache
cert1.pem chain1.pem fullchain1.pem privkey1.pem
curl -F "url=https://spend.tk/telegram/setwebhook" -F "[email protected]" "https://api.telegram.org/botAPI/setwebhook"
curl -F "url=https://spend.tk/telegram/setwebhook" -F "[email protected]" "https://api.telegram.org/botAPI/setwebhook"
curl -F "url=https://spend.tk/telegram/setwebhook" -F "[email protected]" "https://api.telegram.org/botAPI/setwebhook"
{"ok":true,"result":true,"description":"Webhook was set"}
{"ok":true,"result":{"url":"https://spend.tk/telegram/setwebhook","has_custom_certificate":true,"pending_update_count":2,"last_error_date":1614020700,"last_error_message":"SSL error {error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed}","max_connections":40,"ip_address":"95.128.xxx.xxx"}}
Answer the question
In order to leave comments, you need to log in
If you break through https://www.ssllabs.com/ssltest/analyze.html?d=spend.tk ,
pay attention to certificate #2 - it is not trusted and, in principle, it should not be. You have an error in the web server configuration.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question