Node-telegram-bot-api: How to deal with russian telegram blocking?

[IzaGz]

How to bypass the telegram block in russia?

[sand123]

I quickly looked through code, and found that all API interactions rely on request-promise package, which supports connection through proxy

var request = require('request-promise').defaults({
    proxy:'http://username:password@host:port',
    strictSSL :false
  });

[bortnikov]

I quickly looked through code, and found that all API interactions rely on request-promise package, which supports connection through proxy

How to use it in bot?

[sand123]

request-promise is a wrapper around npm request - see proxy settings
You should try manually edit in /src/telegram.js at line 10:

const request = require('request-promise').defaults(/* http proxy settings here */);

Notice: it supports HTTP(s) proxies only, not socks

[bortnikov]

Thank you. This works

You should try manually edit in /src/telegram.js at line 10:

[samohovets]

Also you can use TelegramBot options like this:

const bot = new TelegramBot(config.get('telegram_token'), {
  polling: true,
  request: {
    // Proxy settings here
    proxy: 'http:/***',
  }
});

[bortnikov]

@samohovets Thank you. This work too.

[IzaGz]

Please suggest which proxy to use?Is there any good free proxies?
@samohovets , @sand123 which proxies do u use? Do you use chargeable proxies?

[Osrx]

Please add support of SOCKS5 proxy.
Socks proxy used as standard proxy method in Telegram app, so it will be more easy to find.

[nskondratev]

@Osrx
You can use SOCKS5 proxy with the socks5-https-client lib. Example:

const TelegramBot = require('node-telegram-bot-api')
const Agent = require('socks5-https-client/lib/Agent')

const bot = new TelegramBot(process.env.TELEGRAM_API_TOKEN, {
    polling: true,
    request: {
        agentClass: Agent,
        agentOptions: {
            socksHost: process.env.PROXY_SOCKS5_HOST,
            socksPort: parseInt(process.env.PROXY_SOCKS5_PORT),
            // If authorization is needed:
            // socksUsername: process.env.PROXY_SOCKS5_USERNAME,
            // socksPassword: process.env.PROXY_SOCKS5_PASSWORD
        }
    }
})

I use this solution to continue developing bot on my local PC (I'm in Russia, so without proxy I can not start bots) and it works.

[IzaGz]

@nskondratev can you please advise which proxies to use?
Do you use free proxy?

[nskondratev]

@IzaGz I set up proxy server on DigitalOcean droplet, which costs $5 per month.

[dappinsight]

one click to bypass Telegram block
https://telegram.solutions

[telegrambotdeveloper]

I use proxy how @nskondratev supposes and have the error: "Unhandled rejection RequestError: Error: connect ECONNREFUSED 127.0.0.1:1080". How can the library call localhost?

[baitun]

@IzaGz you can use Tor Browser as SOCKS5 proxy.
Jast start Tor Browser and use 127.0.0.1:9150 as proxy adress.

[IldarMurzenkov]

@nskondratev
This code works correctly:

var options = {
    url: "https://api.telegram.org/bot1111111...11/getMe",
    agentClass: Agent,
    agentOptions: {
        socksHost: config.proxy.socksHost, 
        socksPort: config.proxy.socksPort,
        socksUsername: config.proxy.socksUsername,
        socksPassword: config.proxy.socksPassword
    }
}
request(options, function (error, res, html) {
  if (!error && res.statusCode == 200) {
    console.log(html)
  }else {
    console.log(error)
  }
})

But when i am trying to use "socks5-https-client" with 'node-telegram-bot-api':

const bot = new TelegramBot(config.bot.token, {
    polling: true,
    request: {
        agentClass: Agent,
        agentOptions: {
            socksHost: config.proxy.socksHost,
            socksPort: config.proxy.socksPort,
            // If authorization is needed:
             socksUsername: config.proxy.socksUsername,
             socksPassword: config.proxy.socksPassword
        }
    }
});

timeout error occurs.

Could you please help to understand why proxy is not working with 'node-telegram-bot-api'?

[likeavenus]

@IldarMurzenkov hi, what is the "config" ? Have same problem "error: [polling_error] {"code":"EFATAL","message":"EFATAL: Error: connect ECONNREFUSED 127.0.0.1:1080"}"