Crawler giving ECONNREFUSED Error
karmansingh opened this issue · 1 comments
I am getting this error after installing.
(node:7) UnhandledPromiseRejectionWarning: RequestError: Error: connect ECONNREFUSED 172.20.0.5:8080
at new RequestError (/node_modules/request-promise-core/lib/errors.js:14:15)
ambar_1 | at Request.plumbing.callback (/node_modules/request-promise-core/lib/plumbing.js:87:29)
ambar_1 | at Request.RP$callback [as _callback] (/node_modules/request-promise-core/lib/plumbing.js:46:31)
ambar_1 | at self.callback (/node_modules/request/request.js:185:22)
ambar_1 | at emitOne (events.js:116:13)
ambar_1 | at Request.emit (events.js:211:7)
ambar_1 | at Request.onRequestError (/node_modules/request/request.js:881:8)
ambar_1 | at emitOne (events.js:116:13)
ambar_1 | at ClientRequest.emit (events.js:211:7)
ambar_1 | at Socket.socketErrorListener (_http_client.js:387:9)
ambar_1 | at emitOne (events.js:116:13)
ambar_1 | at Socket.emit (events.js:211:7)
ambar_1 | at emitErrorNT (internal/streams/destroy.js:64:8)
ambar_1 | at _combinedTickCallback (internal/process/next_tick.js:138:11)
ambar_1 | at process._tickCallback (internal/process/next_tick.js:180:9)
ambar_1 | (node:7) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 35)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.