[GH-ISSUE #267] Crawler giving ECONNREFUSED Error #253

Closed
opened 2026-02-27 15:55:50 +03:00 by kerem · 1 comment
Owner

Originally created by @karmansingh on GitHub (Sep 27, 2019).
Original GitHub issue: https://github.com/RD17/ambar/issues/267

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)

Originally created by @karmansingh on GitHub (Sep 27, 2019). Original GitHub issue: https://github.com/RD17/ambar/issues/267 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)
kerem 2026-02-27 15:55:50 +03:00
  • closed this issue
  • added the
    wontfix
    label
Author
Owner

@stale[bot] commented on GitHub (Oct 12, 2019):

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.

<!-- gh-comment-id:541347706 --> @stale[bot] commented on GitHub (Oct 12, 2019): 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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ambar#253
No description provided.