Драйвер Telegram Adapter
-
https://github.com/Haba1234/ioBroker.telegram ставь эту, в настройках настройки прокси, это ещё тестовая версия
-
копать сюда https://github.com/kirovilya/ioBroker.telegram
сделал PR в основной репозиторий, ждем обновления драйвера
-
Обновил драйвер, да же настроил прокси…...
Но вы итоге......
! host.GoldFish2 2018-05-01 19:57:28.888 info instance system.adapter.telegram.0 started with pid 7164
! host.GoldFish2 2018-05-01 19:57:27.868 info Restart adapter system.adapter.telegram.0 because enabled
! host.GoldFish2 2018-05-01 19:57:27.868 error instance system.adapter.telegram.0 terminated with code 0 (OK)
! host.GoldFish2 2018-05-01 19:57:27.868 error Caught by controller[1]: port: 443 }
! host.GoldFish2 2018-05-01 19:57:27.868 error Caught by controller[1]: address: '88.212.233.100',
! host.GoldFish2 2018-05-01 19:57:27.868 error Caught by controller[1]: syscall: 'connect',
! host.GoldFish2 2018-05-01 19:57:27.867 error Caught by controller[1]: errno: 'ETIMEDOUT',
! host.GoldFish2 2018-05-01 19:57:27.867 error Caught by controller[1]: code: 'ETIMEDOUT',
! host.GoldFish2 2018-05-01 19:57:27.867 error Caught by controller[1]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1087:14)
! host.GoldFish2 2018-05-01 19:57:27.867 error Caught by controller[1]: at exports._exceptionWithHostPort (util.js:1045:20)
! host.GoldFish2 2018-05-01 19:57:27.867 error Caught by controller[1]: at Object.exports._errnoException (util.js:1022:11)
! host.GoldFish2 2018-05-01 19:57:27.867 error Caught by controller[1]: { Error: connect ETIMEDOUT 88.212.233.100:443
! host.GoldFish2 2018-05-01 19:57:27.867 error Caught by controller[1]: port: 443 }
! host.GoldFish2 2018-05-01 19:57:27.867 error Caught by controller[1]: address: '88.212.233.100',
! host.GoldFish2 2018-05-01 19:57:27.867 error Caught by controller[1]: syscall: 'connect',
! host.GoldFish2 2018-05-01 19:57:27.867 error Caught by controller[1]: errno: 'ETIMEDOUT',
! host.GoldFish2 2018-05-01 19:57:27.867 error Caught by controller[1]: code: 'ETIMEDOUT',
! host.GoldFish2 2018-05-01 19:57:27.867 error Caught by controller[1]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1087:14)
! host.GoldFish2 2018-05-01 19:57:27.867 error Caught by controller[1]: at exports._exceptionWithHostPort (util.js:1045:20)
! host.GoldFish2 2018-05-01 19:57:27.867 error Caught by controller[1]: at Object.exports._errnoException (util.js:1022:11)
! host.GoldFish2 2018-05-01 19:57:27.867 error Caught by controller[1]: { Error: connect ETIMEDOUT 88.212.233.100:443
! host.GoldFish2 2018-05-01 19:57:27.867 error Caught by controller[1]: port: 443 }
! host.GoldFish2 2018-05-01 19:57:27.867 error Caught by controller[1]: address: '88.212.233.100',
! host.GoldFish2 2018-05-01 19:57:27.867 error Caught by controller[1]: syscall: 'connect',
! host.GoldFish2 2018-05-01 19:57:27.867 error Caught by controller[1]: errno: 'ETIMEDOUT',
! host.GoldFish2 2018-05-01 19:57:27.867 error Caught by controller[1]: code: 'ETIMEDOUT',
! host.GoldFish2 2018-05-01 19:57:27.867 error Caught by controller[1]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1087:14)
! host.GoldFish2 2018-05-01 19:57:27.867 error Caught by controller[1]: at exports._exceptionWithHostPort (util.js:1045:20)
! host.GoldFish2 2018-05-01 19:57:27.867 error Caught by controller[1]: at Object.exports._errnoException (util.js:1022:11)
! host.GoldFish2 2018-05-01 19:57:27.867 error Caught by controller[1]: { Error: connect ETIMEDOUT 88.212.233.100:443
! host.GoldFish2 2018-05-01 19:57:27.867 error Caught by controller[0]: See https://github.com/yagop/node-telegram- … issues/319. at module.js:570:32
! host.GoldFish2 2018-05-01 19:57:27.866 error Caught by controller[0]: In the future, you will have to enable it yourself.
! host.GoldFish2 2018-05-01 19:57:27.866 error Caught by controller[0]: Tue, 01 May 2018 09:57:05 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
! telegram.0 2018-05-01 19:57:27.354 error Error: connect ETIMEDOUT 88.212.233.100:443 at Object.exports._errnoException (util.js:1022:11) at exports._exceptionWithHostPort (util.js:1045:20) at TCPConnectWrap.afterConnect [as oncom
! telegram.0 2018-05-01 19:57:27.354 error uncaught exception: connect ETIMEDOUT 88.212.233.100:443
! telegram.0 2018-05-01 19:57:27.354 error Error: connect ETIMEDOUT 88.212.233.100:443 at Object.exports._errnoException (util.js:1022:11) at exports._exceptionWithHostPort (util.js:1045:20) at TCPConnectWrap.afterConnect [as oncom
! telegram.0 2018-05-01 19:57:27.354 error uncaught exception: connect ETIMEDOUT 88.212.233.100:443
! telegram.0 2018-05-01 19:57:27.354 error Error: connect ETIMEDOUT 88.212.233.100:443 at Object.exports._errnoException (util.js:1022:11) at exports._exceptionWithHostPort (util.js:1045:20) at TCPConnectWrap.afterConnect [as oncom
! telegram.0 2018-05-01 19:57:27.353 error uncaught exception: connect ETIMEDOUT 88.212.233.100:443
! telegram.0 2018-05-01 19:57:06.323 info starting. Version 1.2.3 in C:/ioBroker/node_modules/iobroker.telegram, node: v6.9.5
! host.GoldFish2 2018-05-01 19:56:56.386 info instance system.adapter.telegram.0 started with pid 7240
! host.GoldFish2 2018-05-01 19:56:55.357 info Restart adapter system.adapter.telegram.0 because enabledКуда рыть дальше??? Или какой прокси использовать??
-
Добрый день тоже сыпятся ошибки при настройки прокси:
! host.orangepipcplus 2018-05-09 12:22:13.425 error instance system.adapter.telegram.0 terminated with code 0 (OK)
! Caught 2018-05-09 12:22:13.425 error by controller[3]: at TCP.onread (net.js:607:20) code: 'EAUTHNOTSUPPORT' }
! Caught 2018-05-09 12:22:13.425 error by controller[3]: at Socket.Readable.push (_stream_readable.js:208:10)
! Caught 2018-05-09 12:22:13.425 error by controller[3]: at readableAddChunk (_stream_readable.js:250:11)
! Caught 2018-05-09 12:22:13.424 error by controller[3]: at addChunk (_stream_readable.js:263:12)
! Caught 2018-05-09 12:22:13.424 error by controller[3]: at Socket.emit (events.js:211:7)
! Caught 2018-05-09 12:22:13.424 error by controller[3]: at emitOne (events.js:116:13)
! Caught 2018-05-09 12:22:13.424 error by controller[3]: at Socket.Parser.__onData (/opt/iobroker/node_modules/iobroker.telegram/node_modules/socksv5/lib/client.parser.js:33:10)
! Caught 2018-05-09 12:22:13.423 error by controller[3]: at Parser._onData (/opt/iobroker/node_modules/iobroker.telegram/node_modules/socksv5/lib/client.parser.js:85:14)
! Caught 2018-05-09 12:22:13.423 error by controller[3]: at Parser.emit (events.js:211:7)
! Caught 2018-05-09 12:22:13.423 error by controller[3]: at emitOne (events.js:116:13)
! Caught 2018-05-09 12:22:13.423 error by controller[3]: at Parser. <anonymous>(/opt/iobroker/node_modules/iobroker.telegram/node_modules/socksv5/lib/client.js:102:15)
! Caught 2018-05-09 12:22:13.422 error by controller[3]: { Error: Authentication method mismatch
! Caught 2018-05-09 12:22:13.422 error by controller[2]: at TCP.onread (net.js:607:20) code: 'EAUTHNOTSUPPORT' }
! Caught 2018-05-09 12:22:13.422 error by controller[2]: at Socket.Readable.push (_stream_readable.js:208:10)
! Caught 2018-05-09 12:22:13.422 error by controller[2]: at readableAddChunk (_stream_readable.js:250:11)
! Caught 2018-05-09 12:22:13.421 error by controller[2]: at addChunk (_stream_readable.js:263:12)
! Caught 2018-05-09 12:22:13.421 error by controller[2]: at Socket.emit (events.js:211:7)
! Caught 2018-05-09 12:22:13.421 error by controller[2]: at emitOne (events.js:116:13)
! Caught 2018-05-09 12:22:13.421 error by controller[2]: at Socket.Parser.__onData (/opt/iobroker/node_modules/iobroker.telegram/node_modules/socksv5/lib/client.parser.js:33:10)
! Caught 2018-05-09 12:22:13.420 error by controller[2]: at Parser._onData (/opt/iobroker/node_modules/iobroker.telegram/node_modules/socksv5/lib/client.parser.js:85:14)
! Caught 2018-05-09 12:22:13.420 error by controller[2]: at Parser.emit (events.js:211:7)
! Caught 2018-05-09 12:22:13.420 error by controller[2]: at emitOne (events.js:116:13)
! Caught 2018-05-09 12:22:13.420 error by controller[2]: at Parser. <anonymous>(/opt/iobroker/node_modules/iobroker.telegram/node_modules/socksv5/lib/client.js:102:15)
! Caught 2018-05-09 12:22:13.420 error by controller[2]: { Error: Authentication method mismatch
! Caught 2018-05-09 12:22:13.419 error by controller[1]: at TCP.onread (net.js:607:20) code: 'EAUTHNOTSUPPORT' }
! Caught 2018-05-09 12:22:13.419 error by controller[1]: at Socket.Readable.push (_stream_readable.js:208:10)
! Caught 2018-05-09 12:22:13.419 error by controller[1]: at readableAddChunk (_stream_readable.js:250:11)
! Caught 2018-05-09 12:22:13.419 error by controller[1]: at addChunk (_stream_readable.js:263:12)
! Caught 2018-05-09 12:22:13.418 error by controller[1]: at Socket.emit (events.js:211:7)
! Caught 2018-05-09 12:22:13.418 error by controller[1]: at emitOne (events.js:116:13)
! Caught 2018-05-09 12:22:13.418 error by controller[1]: at Socket.Parser.__onData (/opt/iobroker/node_modules/iobroker.telegram/node_modules/socksv5/lib/client.parser.js:33:10)
! Caught 2018-05-09 12:22:13.418 error by controller[1]: at Parser._onData (/opt/iobroker/node_modules/iobroker.telegram/node_modules/socksv5/lib/client.parser.js:85:14)
! Caught 2018-05-09 12:22:13.417 error by controller[1]: at Parser.emit (events.js:211:7)
! Caught 2018-05-09 12:22:13.417 error by controller[1]: at emitOne (events.js:116:13)
! Caught 2018-05-09 12:22:13.417 error by controller[1]: at Parser. <anonymous>(/opt/iobroker/node_modules/iobroker.telegram/node_modules/socksv5/lib/client.js:102:15)
! Caught 2018-05-09 12:22:13.417 error by controller[1]: { Error: Authentication method mismatch
! Caught 2018-05-09 12:22:13.416 error by controller[0]: See https://github.com/yagop/node-telegram- … issues/319. at module.js:652:30
! Caught 2018-05-09 12:22:13.416 error by controller[0]: In the future, you will have to enable it yourself.
! Caught 2018-05-09 12:22:13.415 error by controller[0]: Wed, 09 May 2018 02:22:11 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
! telegram.0 2018-05-09 12:22:13.324 info terminating
! telegram.0 2018-05-09 12:22:12.816 error at TCP.onread (net.js:607:20)
! telegram.0 2018-05-09 12:22:12.816 error at Socket.Readable.push (_stream_readable.js:208:10)
! telegram.0 2018-05-09 12:22:12.816 error at readableAddChunk (_stream_readable.js:250:11)
! telegram.0 2018-05-09 12:22:12.816 error at addChunk (_stream_readable.js:263:12)
! telegram.0 2018-05-09 12:22:12.816 error at Socket.emit (events.js:211:7)
! telegram.0 2018-05-09 12:22:12.816 error at emitOne (events.js:116:13)
! telegram.0 2018-05-09 12:22:12.816 error at Socket.Parser.__onData (/opt/iobroker/node_modules/iobroker.telegram/node_modules/socksv5/lib/client.parser.js:33:10)
! telegram.0 2018-05-09 12:22:12.816 error at Parser._onData (/opt/iobroker/node_modules/iobroker.telegram/node_modules/socksv5/lib/client.parser.js:85:14)
! telegram.0 2018-05-09 12:22:12.816 error at Parser.emit (events.js:211:7)
! telegram.0 2018-05-09 12:22:12.816 error at emitOne (events.js:116:13)
! telegram.0 2018-05-09 12:22:12.816 error at Parser. <anonymous>(/opt/iobroker/node_modules/iobroker.telegram/node_modules/socksv5/lib/client.js:102:15)
! telegram.0 2018-05-09 12:22:12.816 error Error: Authentication method mismatch
! telegram.0 2018-05-09 12:22:12.815 error uncaught exception: Authentication method mismatch
! telegram.0 2018-05-09 12:22:12.809 error at TCP.onread (net.js:607:20)
! telegram.0 2018-05-09 12:22:12.809 error at Socket.Readable.push (_stream_readable.js:208:10)
! telegram.0 2018-05-09 12:22:12.809 error at readableAddChunk (_stream_readable.js:250:11)
! telegram.0 2018-05-09 12:22:12.809 error at addChunk (_stream_readable.js:263:12)
! telegram.0 2018-05-09 12:22:12.809 error at Socket.emit (events.js:211:7)
! telegram.0 2018-05-09 12:22:12.809 error at emitOne (events.js:116:13)
! telegram.0 2018-05-09 12:22:12.809 error at Socket.Parser.__onData (/opt/iobroker/node_modules/iobroker.telegram/node_modules/socksv5/lib/client.parser.js:33:10)
! telegram.0 2018-05-09 12:22:12.809 error at Parser._onData (/opt/iobroker/node_modules/iobroker.telegram/node_modules/socksv5/lib/client.parser.js:85:14)
! telegram.0 2018-05-09 12:22:12.809 error at Parser.emit (events.js:211:7)
! telegram.0 2018-05-09 12:22:12.809 error at emitOne (events.js:116:13)
! telegram.0 2018-05-09 12:22:12.809 error at Parser. <anonymous>(/opt/iobroker/node_modules/iobroker.telegram/node_modules/socksv5/lib/client.js:102:15)
! telegram.0 2018-05-09 12:22:12.809 error Error: Authentication method mismatch
! telegram.0 2018-05-09 12:22:12.808 error uncaught exception: Authentication method mismatch
! telegram.0 2018-05-09 12:22:12.798 error at TCP.onread (net.js:607:20)
! telegram.0 2018-05-09 12:22:12.798 error at Socket.Readable.push (_stream_readable.js:208:10)
! telegram.0 2018-05-09 12:22:12.798 error at readableAddChunk (_stream_readable.js:250:11)
! telegram.0 2018-05-09 12:22:12.798 error at addChunk (_stream_readable.js:263:12)
! telegram.0 2018-05-09 12:22:12.798 error at Socket.emit (events.js:211:7)
! telegram.0 2018-05-09 12:22:12.798 error at emitOne (events.js:116:13)
! telegram.0 2018-05-09 12:22:12.798 error at Socket.Parser.__onData (/opt/iobroker/node_modules/iobroker.telegram/node_modules/socksv5/lib/client.parser.js:33:10)
! telegram.0 2018-05-09 12:22:12.798 error at Parser._onData (/opt/iobroker/node_modules/iobroker.telegram/node_modules/socksv5/lib/client.parser.js:85:14)
! telegram.0 2018-05-09 12:22:12.798 error at Parser.emit (events.js:211:7)
! telegram.0 2018-05-09 12:22:12.798 error at emitOne (events.js:116:13)
! telegram.0 2018-05-09 12:22:12.798 error at Parser. <anonymous>(/opt/iobroker/node_modules/iobroker.telegram/node_modules/socksv5/lib/client.js:102:15)
! telegram.0 2018-05-09 12:22:12.798 error Error: Authentication method mismatch
! telegram.0 2018-05-09 12:22:12.796 error uncaught exception: Authentication method mismatch</anonymous></anonymous></anonymous></anonymous></anonymous></anonymous>
Кто подскажет где копать? -
Похоже, что-то не так с прокси.
Попробуй такой прокси:
Server: socks.kuzmitch.ru
Port: 1080
User: socksuser
Pass: heropass2
-
Похоже, что-то не так с прокси.
Попробуй такой прокси:
Server: socks.kuzmitch.ru
Port: 1080
User: socksuser
Pass: heropass2 `
И с этим не хотит но ошибка уже другая, такая же как и без прокси! telegram.0 2018-05-11 04:33:59.911 error polling_error:EFATAL, EFATAL: Error: self signed certificate
! telegram.0 2018-05-11 04:33:58.560 info starting. Version 1.2.3 in /opt/iobroker/node_modules/iobroker.telegram, node: v8.11.1
причем когда останавливаешь бота Telegramm сыпятся ошибки! host.orangepipcplus 2018-05-11 04:54:45.766 info instance system.adapter.telegram.0 terminated with code 0 (OK)
! Caught 2018-05-11 04:54:45.766 error by controller[1]: at process._tickCallback (internal/process/next_tick.js:180:9)
! Caught 2018-05-11 04:54:45.765 error by controller[1]: at _combinedTickCallback (internal/process/next_tick.js:138:11)
! Caught 2018-05-11 04:54:45.765 error by controller[1]: at emitErrorNT (internal/streams/destroy.js:64:8)
! Caught 2018-05-11 04:54:45.765 error by controller[1]: at TLSSocket.emit (events.js:211:7)
! Caught 2018-05-11 04:54:45.765 error by controller[1]: at emitOne (events.js:116:13)
! Caught 2018-05-11 04:54:45.764 error by controller[1]: at TLSSocket.socketErrorListener (_http_client.js:387:9)
! Caught 2018-05-11 04:54:45.764 error by controller[1]: at ClientRequest.emit (events.js:211:7)
! Caught 2018-05-11 04:54:45.764 error by controller[1]: at emitOne (events.js:116:13)
! Caught 2018-05-11 04:54:45.764 error by controller[1]: at Request.onRequestError (/opt/iobroker/node_modules/iobroker.telegram/node_modules/node-telegram-bot-api/node_modules/request/request.js:878:8)
! Caught 2018-05-11 04:54:45.763 error by controller[1]: at Request.emit (events.js:211:7)
! Caught 2018-05-11 04:54:45.763 error by controller[1]: at emitOne (events.js:116:13)
! Caught 2018-05-11 04:54:45.763 error by controller[1]: at self.callback (/opt/iobroker/node_modules/iobroker.telegram/node_modules/node-telegram-bot-api/node_modules/request/request.js:186:22)
! Caught 2018-05-11 04:54:45.763 error by controller[1]: at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/iobroker.telegram/node_modules/node-telegram-bot-api/node_modules/request-promise/node_modules/request-promise-
! Caught 2018-05-11 04:54:45.763 error by controller[1]: at Request.plumbing.callback (/opt/iobroker/node_modules/iobroker.telegram/node_modules/node-telegram-bot-api/node_modules/request-promise/node_modules/request-promise-core/lib/
! Caught 2018-05-11 04:54:45.762 error by controller[1]: at new RequestError (/opt/iobroker/node_modules/iobroker.telegram/node_modules/node-telegram-bot-api/node_modules/request-promise/node_modules/request-promise-core/lib/errors.js
! Caught 2018-05-11 04:54:45.762 error by controller[1]: Unhandled rejection RequestError: Error: self signed certificate
! Caught 2018-05-11 04:54:45.762 error by controller[1]: at process._tickCallback (internal/process/next_tick.js:180:9)
! Caught 2018-05-11 04:54:45.762 error by controller[1]: at _combinedTickCallback (internal/process/next_tick.js:138:11)
! Caught 2018-05-11 04:54:45.761 error by controller[1]: at emitErrorNT (internal/streams/destroy.js:64:8)
! Caught 2018-05-11 04:54:45.761 error by controller[1]: at TLSSocket.emit (events.js:211:7)
! Caught 2018-05-11 04:54:45.761 error by controller[1]: at emitOne (events.js:116:13)
! Caught 2018-05-11 04:54:45.760 error by controller[1]: at TLSSocket.socketErrorListener (_http_client.js:387:9)
! Caught 2018-05-11 04:54:45.760 error by controller[1]: at ClientRequest.emit (events.js:211:7)
! Caught 2018-05-11 04:54:45.760 error by controller[1]: at emitOne (events.js:116:13)
! Caught 2018-05-11 04:54:45.759 error by controller[1]: at Request.onRequestError (/opt/iobroker/node_modules/iobroker.telegram/node_modules/node-telegram-bot-api/node_modules/request/request.js:878:8)
! Caught 2018-05-11 04:54:45.759 error by controller[1]: at Request.emit (events.js:211:7)
! Caught 2018-05-11 04:54:45.759 error by controller[1]: at emitOne (events.js:116:13)
! Caught 2018-05-11 04:54:45.759 error by controller[1]: at self.callback (/opt/iobroker/node_modules/iobroker.telegram/node_modules/node-telegram-bot-api/node_modules/request/request.js:186:22)
! Caught 2018-05-11 04:54:45.758 error by controller[1]: at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/iobroker.telegram/node_modules/node-telegram-bot-api/node_modules/request-promise/node_modules/request-promise-
! Caught 2018-05-11 04:54:45.758 error by controller[1]: at Request.plumbing.callback (/opt/iobroker/node_modules/iobroker.telegram/node_modules/node-telegram-bot-api/node_modules/request-promise/node_modules/request-promise-core/lib/
! Caught 2018-05-11 04:54:45.758 error by controller[1]: at new RequestError (/opt/iobroker/node_modules/iobroker.telegram/node_modules/node-telegram-bot-api/node_modules/request-promise/node_modules/request-promise-core/lib/errors.js
! Caught 2018-05-11 04:54:45.758 error by controller[1]: Unhandled rejection RequestError: Error: self signed certificate
! Caught 2018-05-11 04:54:45.757 error by controller[0]: See https://github.com/yagop/node-telegram- … issues/319. at module.js:652:30
! Caught 2018-05-11 04:54:45.757 error by controller[0]: In the future, you will have to enable it yourself.
! Caught 2018-05-11 04:54:45.756 error by controller[0]: Thu, 10 May 2018 18:54:28 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated. -
у меня драйвер даже через впн не пошел, горит жёлтый и нихрена не работает
-
у меня один из пров РТ. не работает и всё
-
Здравствуйте все.
Пытаюсь подключить Telegram.
Что сделал. Установил драйвер. Зашел в https://web.telegram.org получил API ключ , дальше
попытался получить пароль , не пойму как.
На системе ( У меня Кубик) установил SOCKS5 (dante-server). Запустился вроде работает.
Выхожу в мир через Keenetic ADSL, порт TCP пробросил
Как это все увязать до кучи мозгов не хватает. Помогите пожалуйста.
При запуске telegram.0 в логе получаю ошибки:
! Caught by controller[0]: Sat, 01 Sep 2018 13:14:39 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
! 2018-09-01 16:14:41.959 - [31merror[39m: Caught by controller[0]: In the future, you will have to enable it yourself.
! 2018-09-01 16:14:41.959 - [31merror[39m: Caught by controller[0]: See https://github.com/yagop/node-telegram- … issues/319. at internal/modules/cjs/loader.js:689:30
! 2018-09-01 16:14:41.960 - [31merror[39m: Caught by controller[1]: { Error: connection not allowed by ruleset
! 2018-09-01 16:14:41.960 - [31merror[39m: Caught by controller[1]: at Parser._onData (/opt/iobroker/node_modules/socksv5/lib/client.parser.js:122:21)
! 2018-09-01 16:14:41.960 - [31merror[39m: Caught by controller[1]: at Socket.Parser.__onData (/opt/iobroker/node_modules/socksv5/lib/client.parser.js:33:10)
! 2018-09-01 16:14:41.960 - [31merror[39m: Caught by controller[1]: at Socket.emit (events.js:182:13)
! 2018-09-01 16:14:41.961 - [31merror[39m: Caught by controller[1]: at addChunk (_stream_readable.js:283:12)
! 2018-09-01 16:14:41.961 - [31merror[39m: Caught by controller[1]: at readableAddChunk (_stream_readable.js:264:11)
! 2018-09-01 16:14:41.961 - [31merror[39m: Caught by controller[1]: at Socket.Readable.push (_stream_readable.js:219:10)
! 2018-09-01 16:14:41.961 - [31merror[39m: Caught by controller[1]: at TCP.onread (net.js:639:20) code: 'EACCES' }
! 2018-09-01 16:14:41.962 - [31merror[39m: Caught by controller[2]: { Error: connection not allowed by ruleset
! 2018-09-01 16:14:41.962 - [31merror[39m: Caught by controller[2]: at Parser._onData (/opt/iobroker/node_modules/socksv5/lib/client.parser.js:122:21)
! 2018-09-01 16:14:41.962 - [31merror[39m: Caught by controller[2]: at Socket.Parser.__onData (/opt/iobroker/node_modules/socksv5/lib/client.parser.js:33:10)
! 2018-09-01 16:14:41.962 - [31merror[39m: Caught by controller[2]: at Socket.emit (events.js:182:13)
! 2018-09-01 16:14:41.963 - [31merror[39m: Caught by controller[2]: at addChunk (_stream_readable.js:283:12)
! 2018-09-01 16:14:41.963 - [31merror[39m: Caught by controller[2]: at readableAddChunk (_stream_readable.js:264:11)
! 2018-09-01 16:14:41.963 - [31merror[39m: Caught by controller[2]: at Socket.Readable.push (_stream_readable.js:219:10)
! 2018-09-01 16:14:41.963 - [31merror[39m: Caught by controller[2]: at TCP.onread (net.js:639:20) code: 'EACCES' }
! 2018-09-01 16:14:41.964 - [31merror[39m: Caught by controller[3]: { Error: connection not allowed by ruleset
! 2018-09-01 16:14:41.964 - [31merror[39m: Caught by controller[3]: at Parser._onData (/opt/iobroker/node_modules/socksv5/lib/client.parser.js:122:21)
! 2018-09-01 16:14:41.964 - [31merror[39m: Caught by controller[3]: at Socket.Parser.__onData (/opt/iobroker/node_modules/socksv5/lib/client.parser.js:33:10)
! 2018-09-01 16:14:41.964 - [31merror[39m: Caught by controller[3]: at Socket.emit (events.js:182:13)
! 2018-09-01 16:14:41.965 - [31merror[39m: Caught by controller[3]: at addChunk (_stream_readable.js:283:12)
! 2018-09-01 16:14:41.965 - [31merror[39m: Caught by controller[3]: at readableAddChunk (_stream_readable.js:264:11)
! 2018-09-01 16:14:41.965 - [31merror[39m: Caught by controller[3]: at Socket.Readable.push (_stream_readable.js:219:10)
! 2018-09-01 16:14:41.965 - [31merror[39m: Caught by controller[3]: at TCP.onread (net.js:639:20) code: 'EACCES' }
! 2018-09-01 16:14:41.966 - [31merror[39m: host.cubie instance system.adapter.telegram.0 terminated with code 0 (OK)
! 2018-09-01 16:14:41.966 - [32minfo[39m: host.cubie Restart adapter system.adapter.telegram.0 because enabled
! 2018-09-01 16:14:43.011 - [32minfo[39m: host.cubie instance system.adapter.telegram.0 started with pid 14390
! 2018-09-01 16:14:49.076 - [32minfo[39m: telegram.0 starting. Version 1.2.7 in /opt/iobroker/node_modules/iobroker.telegram, node: v10.9.0
! 2018-09-01 16:14:50.097 - [31merror[39m: telegram.0 uncaught exception: connection not allowed by ruleset
! 2018-09-01 16:14:50.103 - [31merror[39m: telegram.0 Error: connection not allowed by ruleset
! at Parser._onData (/opt/iobroker/node_modules/socksv5/lib/client.parser.js:122:21)
! at Socket.Parser.__onData (/opt/iobroker/node_modules/socksv5/lib/client.parser.js:33:10)
! at Socket.emit (events.js:182:13)
! at addChunk (_stream_readable.js:283:12)
! at readableAddChunk (_stream_readable.js:264:11)
! at Socket.Readable.push (_stream_readable.js:219:10)
! at TCP.onread (net.js:639:20)
Ходил по адресу https://github.com/yagop/node-telegram- … issues/319 , но ни чего так и не понял. -
дальше
попытался получить пароль , не пойму как.
Ходил по адресу https://github.com/yagop/node-telegram- … issues/319 , но ни чего так и не понял. `
пароль задаешь свой, при конекте бот его спросит
-
дальше
попытался получить пароль , не пойму как.
Ходил по адресу https://github.com/yagop/node-telegram- … issues/319 , но ни чего так и не понял. `
пароль задаешь свой, при конекте бот его спросит `
Бот ни чего не просит.В proxy пароль даю свой который в danted прописал.
-
все настройки -
Эти настройки я делаю , но значок горит желтым.
В логе " telegram.0 polling_error:EFATAL, EFATAL: Error: connect ETIMEDOUT 149.154.167.220:443"
-
Эти настройки я делаю , но значок горит желтым.
В логе " telegram.0 polling_error:EFATAL, EFATAL: Error: connect ETIMEDOUT 149.154.167.220:443" `
провайдер блокирует, в России у многих так
приходится телеграмм трафик заворачивать в впн канал, еще есть место с подменой днс
-
Эти настройки я делаю , но значок горит желтым.
В логе " telegram.0 polling_error:EFATAL, EFATAL: Error: connect ETIMEDOUT 149.154.167.220:443" `
провайдер блокирует, в России у многих так
приходится телеграмм трафик заворачивать в впн канал, еще есть место с подменой днс `
Я это из лога понял.
Как это обойти?
Пробую danted не получается, в логе отправляют https://github.com/yagop/node-telegram- … issues/319.
А там чего делать не понятно (англицкий на уровне - ниже плинтуса :D )
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren AnmeldenSupport us
328
Online32.7k
Benutzer82.6k
Themen1.3m
Beiträge