From e2fea1ad57ad10e0b6943580f23075c294628f7f Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Mon, 15 May 2023 15:56:31 +0000 Subject: [PATCH] Update content of files --- data/web/blogfork.telegram.org/bots/webhooks.html | 6 ++++-- data/web/core.telegram.org/bots/webhooks.html | 6 ++++-- data/web/corefork.telegram.org/bots/webhooks.html | 6 ++++-- 3 files changed, 12 insertions(+), 6 deletions(-) diff --git a/data/web/blogfork.telegram.org/bots/webhooks.html b/data/web/blogfork.telegram.org/bots/webhooks.html index 3f97f3960f..78a473ec0f 100644 --- a/data/web/blogfork.telegram.org/bots/webhooks.html +++ b/data/web/blogfork.telegram.org/bots/webhooks.html @@ -70,7 +70,7 @@

  • An open port

    A webhook needs an open port on your server. We currently support the following ports: 443, 80, 88 and 8443. Other ports are not supported and will not work. Make sure your bot is running on one of those supported ports, and that the bot is reachable via its public address.

    -
    If you want to limit access to Telegram only, please allow traffic from 149.154.167.197-233 (starting July 2019 please use: 149.154.160.0/20 and 91.108.4.0/22). 
+
    If you want to limit access to Telegram only, please allow traffic from 149.154.160.0/20 and 91.108.4.0/22. 
 Whenever something stops working in the future, please check this document again as 
 the range might expand or change.
    
 
    How do I check for open ports or limit access to my bot?
    
@@ -143,7 +143,9 @@ On a Debian based system the iptables-persistent package is be a good option.
 RHEL/CentOS offers a service iptables save -command.
 A quick online search for "YOUROPERATINGSYSTEM save iptables" also helps.

    That’s all for our examples. More information on best practices for setting up your firewall, on whichever operating system you prefer for your bot, is best found on the internet.

    SSL/TLS, what is it and why do I have to handle this for a webhook?
    diff --git a/data/web/core.telegram.org/bots/webhooks.html b/data/web/core.telegram.org/bots/webhooks.html index 170c8cb6bf..078b7f3240 100644 --- a/data/web/core.telegram.org/bots/webhooks.html +++ b/data/web/core.telegram.org/bots/webhooks.html @@ -70,7 +70,7 @@

  • An open port

    A webhook needs an open port on your server. We currently support the following ports: 443, 80, 88 and 8443. Other ports are not supported and will not work. Make sure your bot is running on one of those supported ports, and that the bot is reachable via its public address.

    -
    If you want to limit access to Telegram only, please allow traffic from 149.154.167.197-233 (starting July 2019 please use: 149.154.160.0/20 and 91.108.4.0/22). 
+
    If you want to limit access to Telegram only, please allow traffic from 149.154.160.0/20 and 91.108.4.0/22. 
 Whenever something stops working in the future, please check this document again as 
 the range might expand or change.
    
 
    How do I check for open ports or limit access to my bot?
    
@@ -143,7 +143,9 @@ On a Debian based system the iptables-persistent package is be a good option.
 RHEL/CentOS offers a service iptables save -command.
 A quick online search for "YOUROPERATINGSYSTEM save iptables" also helps.

    That’s all for our examples. More information on best practices for setting up your firewall, on whichever operating system you prefer for your bot, is best found on the internet.

    SSL/TLS, what is it and why do I have to handle this for a webhook?
    diff --git a/data/web/corefork.telegram.org/bots/webhooks.html b/data/web/corefork.telegram.org/bots/webhooks.html index 514cc5d670..d24e9a6dc4 100644 --- a/data/web/corefork.telegram.org/bots/webhooks.html +++ b/data/web/corefork.telegram.org/bots/webhooks.html @@ -70,7 +70,7 @@

  • An open port

    A webhook needs an open port on your server. We currently support the following ports: 443, 80, 88 and 8443. Other ports are not supported and will not work. Make sure your bot is running on one of those supported ports, and that the bot is reachable via its public address.

    -
    If you want to limit access to Telegram only, please allow traffic from 149.154.167.197-233 (starting July 2019 please use: 149.154.160.0/20 and 91.108.4.0/22). 
+
    If you want to limit access to Telegram only, please allow traffic from 149.154.160.0/20 and 91.108.4.0/22. 
 Whenever something stops working in the future, please check this document again as 
 the range might expand or change.
    
 
    How do I check for open ports or limit access to my bot?
    
@@ -143,7 +143,9 @@ On a Debian based system the iptables-persistent package is be a good option.
 RHEL/CentOS offers a service iptables save -command.
 A quick online search for "YOUROPERATINGSYSTEM save iptables" also helps.

    That’s all for our examples. More information on best practices for setting up your firewall, on whichever operating system you prefer for your bot, is best found on the internet.

    SSL/TLS, what is it and why do I have to handle this for a webhook?