search

windkh / node-red-contrib-telegrambot

Telegram bot nodes for node-red.
Other
256 stars 116 forks source link

Stopped working, Need HELP!! #321

Closed itsboo07 closed 10 months ago

itsboo07 commented 11 months ago

I have been using the bot for some months but last 1 month I have been facing issues with my automations based on telegram bot. it always shows polling and that's not the issue, its showing error when i try to send message also can't able to update the bot, it shows this error. I'm using node red inside home assistant in windows with vm

-----------------------------------------------------------
2023-07-21T11:15:36.278Z Install : node-red-contrib-telegrambot 15.1.4

2023-07-21T11:15:36.724Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red-contrib-telegrambot@15.1.4
2023-07-21T11:15:37.226Z [err] npm
2023-07-21T11:15:37.226Z [err]  WARN config
2023-07-21T11:15:37.226Z [err]  production Use `--omit=dev` instead.
2023-07-21T11:16:50.112Z [err] npm
2023-07-21T11:16:50.112Z [err]  
2023-07-21T11:16:50.112Z [err] ERR!
2023-07-21T11:16:50.113Z [err]  
2023-07-21T11:16:50.113Z [err] code
2023-07-21T11:16:50.113Z [err]  EACCES
2023-07-21T11:16:50.113Z [err] npm
2023-07-21T11:16:50.113Z [err]  
2023-07-21T11:16:50.113Z [err] ERR!
2023-07-21T11:16:50.113Z [err]  
2023-07-21T11:16:50.113Z [err] syscall
2023-07-21T11:16:50.113Z [err]  connect
2023-07-21T11:16:50.114Z [err] npm
2023-07-21T11:16:50.114Z [err]  
2023-07-21T11:16:50.114Z [err] ERR!
2023-07-21T11:16:50.114Z [err]  
2023-07-21T11:16:50.114Z [err] errno
2023-07-21T11:16:50.114Z [err]  EACCES
2023-07-21T11:16:50.122Z [err] npm
2023-07-21T11:16:50.122Z [err]  
2023-07-21T11:16:50.122Z [err] ERR!
2023-07-21T11:16:50.122Z [err]  FetchError: request to https://registry.npmjs.org/node-red-contrib-telegrambot failed, reason: connect EACCES 2606:4700:8393:80e2:e439:4:6810:1023:443
2023-07-21T11:16:50.125Z [err] npm ERR!     at ClientRequest.<anonymous> (/usr/lib/node_modules/npm/node_modules/minipass-fetch/lib/index.js:130:14)
2023-07-21T11:16:50.125Z [err] npm ERR!     at ClientRequest.emit (node:events:513:28)
2023-07-21T11:16:50.125Z [err] npm ERR!     at TLSSocket.socketErrorListener (node:_http_client:502:9)
2023-07-21T11:16:50.125Z [err] npm ERR!     at TLSSocket.emit (node:events:525:35)
2023-07-21T11:16:50.125Z [err] npm ERR!
2023-07-21T11:16:50.125Z [err]      at emitErrorNT (node:internal/streams/destroy:151:8)
2023-07-21T11:16:50.125Z [err] npm ERR!     at emitErrorCloseNT (node:internal/streams/destroy:116:3)
2023-07-21T11:16:50.125Z [err] npm
2023-07-21T11:16:50.126Z [err]  ERR!     at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
2023-07-21T11:16:50.126Z [err] npm ERR!  FetchError: request to https://registry.npmjs.org/node-red-contrib-telegrambot failed, reason: connect EACCES 2606:4700:8393:80e2:e439:4:6810:1023:443
2023-07-21T11:16:50.126Z [err] npm ERR!     at ClientRequest.<anonymous> (/usr/lib/node_modules/npm/node_modules/minipass-fetch/lib/index.js:130:14)
2023-07-21T11:16:50.126Z [err] npm ERR!     at ClientRequest.emit (node:events:513:28)
2023-07-21T11:16:50.126Z [err] npm ERR!     at TLSSocket.socketErrorListener (node:_http_client:502:9)
2023-07-21T11:16:50.126Z [err] npm
2023-07-21T11:16:50.126Z [err]  ERR!     at TLSSocket.emit (node:events:525:35)
2023-07-21T11:16:50.126Z [err] npm ERR!     at emitErrorNT (node:internal/streams/destroy:151:8)
2023-07-21T11:16:50.126Z [err] npm ERR!     at emitErrorCloseNT (node:internal/streams/destroy:116:3)
2023-07-21T11:16:50.126Z [err] npm ERR!     at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
2023-07-21T11:16:50.126Z [err] npm
2023-07-21T11:16:50.126Z [err]  ERR!   code: 'EACCES',
2023-07-21T11:16:50.126Z [err] npm ERR!   errno: 'EACCES',
2023-07-21T11:16:50.126Z [err] npm 
2023-07-21T11:16:50.126Z [err] ERR!   syscall: 'connect',
2023-07-21T11:16:50.126Z [err] npm ERR!   address: '2606:4700:8393:80e2:e439:4:6810:1023',
2023-07-21T11:16:50.126Z [err] npm
2023-07-21T11:16:50.126Z [err]  ERR!   port: 443,
2023-07-21T11:16:50.126Z [err] npm ERR!   type: 'system',
2023-07-21T11:16:50.126Z [err] npm
2023-07-21T11:16:50.126Z [err]  ERR!   requiredBy: '.'
2023-07-21T11:16:50.126Z [err] npm ERR! }
2023-07-21T11:16:50.126Z [err] npm ERR! 
2023-07-21T11:16:50.126Z [err] npm 
2023-07-21T11:16:50.126Z [err] ERR! The operation was rejected by your operating system.
2023-07-21T11:16:50.126Z [err] npm ERR! It is likely you do not have the permissions to access this file as the current user
2023-07-21T11:16:50.126Z [err] npm ERR! 
2023-07-21T11:16:50.126Z [err] npm ERR! If you believe this might be a permissions issue, please double-check the
2023-07-21T11:16:50.126Z [err] npm ERR! permissions of the file and its containing directories, or try running
2023-07-21T11:16:50.126Z [err] npm ERR! the command again as root/Administrator.
2023-07-21T11:16:50.128Z [err] 
2023-07-21T11:16:50.128Z [err] npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2023-07-21T11_15_37_189Z-debug-0.log
2023-07-21T11:16:50.141Z rc=1

also when i send a message i get this error in debug node

Caught exception in sender node:
Error: EFATAL: Error: connect EACCES 2001:67c:4e8:f004::9:443
when processing message:
windkh commented 11 months ago

Looks like a permission problem

windkh commented 10 months ago

@itsboo07 any news?