Launch of the Botá server for Telegram with OpenSSL



  • For a few days now, I've been trying to launch a telegram server, more than three servers:

    1. Heroku's server, his test, he's doing a great job, his web hook's set, the bo's answering.
    2. It wasn't me that silvered in the corporate network, but I didn't do the network configuration, but the port of '88 was abandoned, outside the ip and this port in the browser at https. Apache has been set up, set up, built me, access to everything, self-signed certificate I have generated.
    3. After the failure of the second option, he assumed that the problem was online. For this house, I pay for the static ip, run the port, set up the linux, apache, build ssl, into this ip from the outside on my web site at https, work, website huk, set up, PC results, but bot doesn't answer.

    In logs /var/log/apache2/access.log infa on only brouses, information that telegrams were not available.

    Can there be a problem? I've changed the entire Internet, I'm doing everything in the charts described, both in the telegram boards and others. Doing like that. https://ru.stackoverflow.com/questions/460030/%D0%97%D0%B0%D0%BF%D1%83%D1%81%D0%BA-%D1%81%D0%B5%D1%80%D0%B2%D0%B5%D1%80%D0%B0-%D0%B1%D0%BE%D1%82%D0%BE%D0%B2-%D0%B4%D0%BB%D1%8F-telegram-%D0%BD%D0%B0-openssl



  • In my case, it was necessary to secure the keys properly:

    openssl req -newkey rsa:2048 -sha256 -nodes -keyout apache.key -x509 -days 365 -out apache.pem -subj "/C=RU/ST=Krasnodar/L=Krasnodar/O=./CN=IP address of my server available from outside."

    And correctly establish webhook:

    curl-F "url= https://ip:port/ "F "certificate=@apache.pem." https://api.telegram.org/botTOKEN/setWebhook




Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2