question-mark
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.

Unhandled rejection Error: 502

See original GitHub issue

I created a bot that’s pretty minimal, it doesn’t go much beyond the simple example. I’m pretty new to node and I can’t really explain why I’m getting the following error:

Unhandled rejection Error: 502:
<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx/1.12.2</center>
</body>
</html>

    at Request.then.resp (/home/myself/src/node_modules/slimbot/src/telegram.js:43:15)
    at tryCatcher (/home/myself/src/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/home/myself/src/node_modules/bluebird/js/release/promise.js:512:31)
    at Promise._settlePromise (/home/myself/src/node_modules/bluebird/js/release/promise.js:569:18)
    at Promise._settlePromise0 (/home/myself/src/node_modules/bluebird/js/release/promise.js:614:10)
    at Promise._settlePromises (/home/myself/src/node_modules/bluebird/js/release/promise.js:693:18)
    at Async._drainQueue (/home/myself/src/node_modules/bluebird/js/release/async.js:133:16)
    at Async._drainQueues (/home/myself/src/node_modules/bluebird/js/release/async.js:143:10)
    at Immediate.Async.drainQueues (/home/myself/src/node_modules/bluebird/js/release/async.js:17:14)
    at runCallback (timers.js:794:20)
    at tryOnImmediate (timers.js:752:5)
    at processImmediate [as _immediateCallback] (timers.js:729:5)

Might this be a bug related to this project?

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:6 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
KnorpelSenfcommented, Apr 24, 2018

So I simply catch it and everything is fine? That was too easy … sorry for bothering you with such a beginner question, I didn’t know better.

0reactions
edisoncheecommented, May 23, 2018

Closing this issue as it has been resolved. Please open a new issue if you would like to.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Unhandled rejection Error: 502 · Issue #377 - GitHub
You are simply getting a 502 Bad Gateway error response. My assumption is that Telegram servers use Nginx as a proxy to their...
Read more >
Unhandled rejection Error: status 502: Bad Gateway - Stack Overflow
No information is available for this page.
Read more >
Node.js 502 Bad Gateway Issues and How To Resolve Them
In December of 2018, many Node.js users noticed that their applications randomly returned an HTTP status code 502 “Bad Gateway” error.
Read more >
502 Bad Gateway - HTTP - MDN Web Docs
The HyperText Transfer Protocol (HTTP) 502 Bad Gateway server error response code indicates that the server, while acting as a gateway or ...
Read more >
Bad Gateway" from UnhandledPromiseRejection - Node-RED
I've been down a rabbit hole for a few days here with a 502 Bad Gateway error on my Node-RED. My system's been...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found