Add please socks5 proxy support about iobroker.telegram

[Osrx]

Home Bot stop functioning today...
Russia....

Please add socks proxy support!

[GermanBluefox]

It is wrong place to do that. Here: https://github.com/yagop/node-telegram-bot-api пн, 16 апр. 2018 г., 12:28 Osrx <[email protected]>:

…

Home Bot stop functioning today... Russia.... Please add socks proxy support! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#50 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEXqgAZLoqUnZSaj9AldfJI3xzCk235mks5tpHJegaJpZM4TTMoe> .

[Osrx]

Next text I found in following link: yagop/node-telegram-bot-api#562 <yagop/node-telegram-bot-api#562> Will it helps? Where can we add proxy in iOBroker? 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 }); — С уважением, Хабров Андрей.

…

On 17 апр. 2018 г., at 11:18, Bluefox ***@***.***> wrote: It is wrong place to do that. Here: https://github.com/yagop/node-telegram-bot-api пн, 16 апр. 2018 г., 12:28 Osrx ***@***.***>: > Home Bot stop functioning today... > Russia.... > > Please add socks proxy support! > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#50 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AEXqgAZLoqUnZSaj9AldfJI3xzCk235mks5tpHJegaJpZM4TTMoe> > . > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#50 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AYL9fSIx0GP6KOw6VTasyC31Jwnx8G9pks5tpaU_gaJpZM4TTMoe>.

[GermanBluefox]

It is interesting. Thank you вт, 17 апр. 2018 г., 10:43 Osrx <[email protected]>:

…

Next text I found in following link: yagop/node-telegram-bot-api#562 < yagop/node-telegram-bot-api#562> Will it helps? Where can we add proxy in iOBroker? 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({ ***@***.***:port', strictSSL :false }); — С уважением, Хабров Андрей. Тел.: [phone] > On 17 апр. 2018 г., at 11:18, Bluefox ***@***.***> wrote: > > It is wrong place to do that. > Here: https://github.com/yagop/node-telegram-bot-api > > пн, 16 апр. 2018 г., 12:28 Osrx ***@***.***>: > > > Home Bot stop functioning today... > > Russia.... > > > > Please add socks proxy support! > > > > — > > You are receiving this because you are subscribed to this thread. > > Reply to this email directly, view it on GitHub > > < #50 (comment) >, > > or mute the thread > > < https://github.com/notifications/unsubscribe-auth/AEXqgAZLoqUnZSaj9AldfJI3xzCk235mks5tpHJegaJpZM4TTMoe > > > . > > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub < #50 (comment)>, or mute the thread < https://github.com/notifications/unsubscribe-auth/AYL9fSIx0GP6KOw6VTasyC31Jwnx8G9pks5tpaU_gaJpZM4TTMoe >. > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#50 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEXqgIYtj7Bpr4BQtaHyMPY67dmKPklTks5tpasYgaJpZM4TTMoe> .

[Osrx]

Also there is a way to implement SOCK5 support to Telegram bot.
Can you add this in your connector?

yagop/node-telegram-bot-api#562 (comment)

[Haba1234]

Hi!

please test socks5 https://github.com/Haba1234/ioBroker.telegram

[Osrx]

I think i do something wrong.
For clear test, I've delete current telegram instance. Also telegram folder was deleted from filesystem.
Install from GitHub folder from URL: https://github.com/Haba1234/ioBroker.telegram

The debug log is:

`

host.cubieboard2	2018-04-18 20:14:23.511	info	Update repository "default" under "http://download.iobroker.net/sources-dist.json"
iobroker	2018-04-18 20:14:22.861	info	exit 0
iobroker	2018-04-18 20:14:22.666	info	└── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], requ
iobroker	2018-04-18 20:14:22.666	info	[email protected] var/opt/iobroker/node_modules/iobroker.telegram├── [email protected] ([email protected])
web.0	2018-04-18 20:13:48.602	info	2018-04-18T17:13:48.601Z Connected system.user.admin
web.0	2018-04-18 20:13:28.979	info	2018-04-18T17:13:28.978Z Connected system.user.admin
iobroker	2018-04-18 20:12:48.495	info	[email protected]: wanted: {"node":">= 6.4.0"} (current: {"node":"4.9.1","npm":"2.15.11"})
iobroker	2018-04-18 20:12:48.488	info	npm WARN engine
iobroker	2018-04-18 20:12:47.515	info	WARN engine [email protected]: wanted: {"node":">= 6.4.0"} (current: {"node":"4.9.1","npm":"2.15.11"})
iobroker	2018-04-18 20:12:47.505	info	npm
iobroker	2018-04-18 20:12:34.959	info	npm install https://github.com/Haba1234/ioBroker.telegram/tarball/master --production --prefix "/var/opt/iobroker" (System call)
iobroker	2018-04-18 20:12:34.050	info	install https://github.com/Haba1234/ioBroker.telegram/tarball/master
`

I see folder structure with changes about socks proxy.
` root@cubieboard2:/var/opt/iobroker/node_modules/iobroker.telegram/admin# cat ./words.js | grep Prox
"Proxy Socks5 enable": { "en": "Proxy Socks5 enable", "de": "Proxy Socks5 aktivieren", "ru": "Включить proxy Socks5", "pt": "Proxy Socks5 ativar", "nl": "Proxy Socks5 inschakelen", "fr": "Proxy Socks5 activer", "it": "Abilita Proxy Socks5", "es": "Proxy Socks5 habilita", "pl": "Włącz Proxy Socks5"},
"proxy Host": { "en": "proxy Host", "de": "Proxy-Host", "ru": "прокси-сервер", "pt": "host proxy", "nl": "Proxy host", "fr": "Hôte proxy", "it": "host proxy", "es": "host proxy", "pl": "Host proxy"},

root@cubieboard2:/var/opt/iobroker/node_modules/iobroker.telegram/admin#`

Also I see that Telegram adapter version 1.2.1 installed in adapter tab.

But I don't see that Telegram.0 instance appears in "Instances" tab...
So I can not configure it. Or check something...

[Haba1234]

after installation with the github, you need to click "plus" (install the driver) on the tab "Drivers"

[Osrx]

Ok.
If I click "+" and adapter installed. But in adapter settings I've see nothing about proxy... =(

There is two files index.html and index_m.html and only in second there is something about Proxy.
If I rename one to another I start to see settings page with proxy settings but there is no Save button...

Where is a problem?

[Haba1234]

Андрей, админка у тебя второй версии что-ли? Драйвер я апгрейдил под третью админку только (index_m.html который). В группе телеграм есть?

[Osrx]

Написано 2.0.9
Ума не приложу как ее обновить. Он не говорит что есть более новая версия я и не обновляю... =(
Ты про какую группу? Название дай.

[kirovilya]

С прокси сейчас работает только отправка текста, а картинки и видео не отправляются.
Нашел упоминание этой же ошибки в используемой библиотеке mattcg/socks5-https-client#22 но решения нет.

[Apollon77]

SHould be done since v1.2.2/1.2.3 ?! Please reopen if not