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.
Better debug/error information
See original GitHub issueFor now there is no good way to handle internal error messages + debugging this errors.
For example:
We have CloudFlare -> Nginx -> Node.js (engine.io ws server) cluster
Pretty often I see such errors:
*3712847 upstream prematurely closed connection while reading response header from upstream, client: 172.31.54.181, server: , request:
But I couldn’t debug this issue because If I’ll enable debug for ws. It will flash me with tones of useless information.
As well on Socket close event I have only forced close message and have no idea why and where. error event is also not fired.
socket closed and transport closed are also not very good info for searching an issue.
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@darrachequesne I’ll try. but not sure about available free time )
Closed due to inactivity, please reopen if needed.