У меня была аналогичная проблема использовал сертификат от letsencrypt. Для работы бота webhook необходимо оценка от A- на
https://www.ssllabs.com/ssltest/analyze.html. В моем случае решение было таким:
./letsencrypt-auto --agree-tos \
--renew-by-default \
--standalone \
--standalone-supported-challenges http-01 \
--http-01-port 9999 \
--server https://acme-v01.api.letsencrypt.org/directory certonly \
--rsa-key-size 4096 \
-d example.com
wget https://letsencrypt.org/certs/lets-encrypt-x3-cross-signed.pem
cat lets-encrypt-x3-cross-signed.pem >> /etc/letsencrypt/live/example.com/fullchain.pem
openssl dhparam -out /etc/ss l/private/dhparams_4096.pem 4096
ssl конфиг nginx
add_header Strict-Transport-Security "max-age=63072000";
add_header X-Frame-Options DENY;
ssl on;
ssl_certificate /etc/letsencrypt/live/example.com/cert.pem;
ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;
ssl_stapling on;
ssl_stapling_verify on;
ssl_trusted_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
resolver 8.8.8.8 8.8.4.4 valid=300s;
resolver_timeout 3s;
ssl_session_cache shared:SSL:100m;
ssl_session_timeout 24h;
ssl_dhparam /etc/ssl/private/dhparams_4096.pem;
ssl_ecdh_curve secp384r1;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_prefer_server_ciphers on;
ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!3DES:!MD5:!PSK';
Как запустить Telegram бота HellowBot?