Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Seems to stop listening after a few days

See original GitHub issue

Hi. Thanks for this library - it’s excellent. Absolutely the best I’ve seen.

We have a bot running on zeit/now.sh, which listens for /commands in a channel.

it seems like every few days, the bot gets a few HTTP errors from Telegram’s API, and stops listening.

The only way to get the bot to respond to commands again is to remove it from the channel and re-add it.

Is this a known issue?

These may not even be related, but it’s all the logs contain:

09/03 04:03 AM (2d)
Failed to get updates. Waiting: 1s { Error: 500: Unsupported message from Telegram
    at buildPayload.then.then.then.then (/home/nowuser/src/node_modules/telegraf/lib/network/client.js:102:17)
    at <anonymous>
    at process._tickDomainCallback (internal/process/next_tick.js:228:7)
  code: 500,
  response: 
   { error_code: 500,
     description: 'Unsupported message from Telegram',
     response: '<html>\r\n<head><title>502 Bad Gateway</title></head>\r\n<body bgcolor="white">\r\n<center><h1>502 Bad Gateway</h1></center>\r\n<hr><center>nginx/1.10.1</center>\r\n</body>\r\n</html>\r\n' },
  description: 'Unsupported message from Telegram',
  parameters: {} }
09/03 04:03 AM (2d)
Failed to get updates. Waiting: 1s { Error: 500: Unsupported message from Telegram
    at buildPayload.then.then.then.then (/home/nowuser/src/node_modules/telegraf/lib/network/client.js:102:17)
    at <anonymous>
    at process._tickDomainCallback (internal/process/next_tick.js:228:7)
  code: 500,
  response: 
   { error_code: 500,
     description: 'Unsupported message from Telegram',
     response: '<html>\r\n<head><title>502 Bad Gateway</title></head>\r\n<body bgcolor="white">\r\n<center><h1>502 Bad Gateway</h1></center>\r\n<hr><center>nginx/1.10.0</center>\r\n</body>\r\n</html>\r\n' },
  description: 'Unsupported message from Telegram',
  parameters: {} }
09/03 04:03 AM (2d)
Failed to get updates. Waiting: 1s { Error: 500: Unsupported message from Telegram
    at buildPayload.then.then.then.then (/home/nowuser/src/node_modules/telegraf/lib/network/client.js:102:17)
    at <anonymous>
    at process._tickDomainCallback (internal/process/next_tick.js:228:7)
  code: 500,
  response: 
   { error_code: 500,
     description: 'Unsupported message from Telegram',
     response: '<html>\r\n<head><title>502 Bad Gateway</title></head>\r\n<body bgcolor="white">\r\n<center><h1>502 Bad Gateway</h1></center>\r\n<hr><center>nginx/1.10.0</center>\r\n</body>\r\n</html>\r\n' },
  description: 'Unsupported message from Telegram',
  parameters: {} }
09/03 04:03 AM (2d)
Failed to get updates. Waiting: 1s { Error: 500: Unsupported message from Telegram
    at buildPayload.then.then.then.then (/home/nowuser/src/node_modules/telegraf/lib/network/client.js:102:17)
    at <anonymous>
    at process._tickDomainCallback (internal/process/next_tick.js:228:7)
  code: 500,
  response: 
   { error_code: 500,
     description: 'Unsupported message from Telegram',
     response: '<html>\r\n<head><title>502 Bad Gateway</title></head>\r\n<body bgcolor="white">\r\n<center><h1>502 Bad Gateway</h1></center>\r\n<hr><center>nginx/1.10.0</center>\r\n</body>\r\n</html>\r\n' },
  description: 'Unsupported message from Telegram',
  parameters: {} }