• The application with the webhuk is from examples from the Telegram.Bot library with the added transfer of the certificate from its own comments.
  • The application is deployed on a virtual in eyjur
  • The self-signed certificate was generated exactly with the instructions from the site telegram with the real domain xxxxxx.cloudapp.net and added to the virtual-certificate storage.
  • PEM has been exported from it and its shipping has been added to the application.
  • On the netsh http add urlacl and netsh http add sslcert according to the comments in the code
  • in the firewall ports are open, points are configured
  • sslshopper shows that this certificate is being given and checks pass, except for the warning that some browsers may swear on such a certificate
  • DOES NOT getWebhookInfo - getWebhookInfo says

ssl3_get_server_certificate: certificate verify failed

As a result, the bot does not respond to the client. Where is the error, what is wrong? everything is taken exactly from the examples, what else is wrong with the certificate?

  • What ports do you use? setWebHook performed? - Anatol
  • Try getWebhookInfo and show us the result. - Anatol
  • Yes, it was somehow strangely connected with the ports. When replaced by 443 everything took off. - Dmdone
  • Ports currently supported for Webhooks: 443, 80, 88, 8443 as if from the documentation. And with what changed? - Anatol
  • one
    This is from the API documentation. And in the current documentation for SetWebHook in the library it was found 3. For the moment, the port for Webhooks is 443. We may support additional ports later. Changed from 8443, which was in the example. - Dmdone

0