This is on theRailway console:
original: Error: getaddrinfo ENOTFOUND undefined
original: Error: getaddrinfo ENOTFOUND undefined
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26) {
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26) {
errno: -3008,
errno: -3008,
code: 'ENOTFOUND',
code: 'ENOTFOUND',
syscall: 'getaddrinfo',
syscall: 'getaddrinfo',
hostname: 'undefined'
hostname: 'undefined'
I follow all the steps to deploy my full-stack app on railway. I first, deployed my db from postgress successfully and pass it the links to my .env on my server side app. Now, looks like the hostname is not working not sure why is this happening.
Related
When I try to run the hosted API app, I get the following message:
2022-04-11T12:32:31: Server running at http://localhost:9000
2022-04-11T12:32:31: Error: getaddrinfo ENOTFOUND localhostss
2022-04-11T12:32:31: at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:71:26) {
2022-04-11T12:32:31: errno: -3008,
2022-04-11T12:32:31: code: 'ENOTFOUND',
2022-04-11T12:32:31: syscall: 'getaddrinfo',
2022-04-11T12:32:31: hostname: 'localhostss',
2022-04-11T12:32:31: fatal: true
2022-04-11T12:32:31: }
Please help me fix
index.js:
enter image description here
hostname is wrong
according to error hostname is localhostss rather than localhost
I'm doing a stress test to my nodejs app, the test basically send a bulk of requests concurrently, sometimes I got this annoying error:
{ RequestError: Error: connect ECONNREFUSED 127.0.0.1:1234
at new RequestError (/mnt/c/Users/rawhi/Desktop/myCode/backend/api/node_modules/request-promise-core/lib/errors.js:14:15)
at Request.plumbing.callback (/mnt/c/Users/rawhi/Desktop/myCode/backend/api/node_modules/request-promise-core/lib/plumbing.js:87:29)
at Request.RP$callback [as _callback] (/mnt/c/Users/rawhi/Desktop/myCode/backend/api/node_modules/request-promise-core/lib/plumbing.js:46:31)
at self.callback (/mnt/c/Users/rawhi/Desktop/myCode/backend/api/node_modules/request/request.js:185:22)
at Request.emit (events.js:198:13)
at Request.onRequestError (/mnt/c/Users/rawhi/Desktop/myCode/backend/api/node_modules/request/request.js:881:8)
at ClientRequest.emit (events.js:198:13)
at Socket.socketErrorListener (_http_client.js:392:9)
at Socket.emit (events.js:198:13)
at emitErrorNT (internal/streams/destroy.js:91:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
at process._tickCallback (internal/process/next_tick.js:63:19)
name: 'RequestError',
message: 'Error: connect ECONNREFUSED 127.0.0.1:1234',
cause:
{ Error: connect ECONNREFUSED 127.0.0.1:1234
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1107:14)
errno: 'ECONNREFUSED',
code: 'ECONNREFUSED',
syscall: 'connect',
address: '127.0.0.1',
port: 1234 }
So the test keeps returning this error for "almost" all the requests, but I still can send requests via postman without any problem.
Can anyone explain me what is the problem here ? and how it can be solved ? like using a queue a proxy or anything else useful ?
Thanks in advance
Error: read ECONNRESET
at TLSWrap.onStreamRead (internal/stream_base_commons.js:111:27) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' } undefined
I am using axios as an HTTP client. When I try to POST on my local server I get this error message:
{ Error: connect ECONNREFUSED 127.0.0.1:80
at Object._errnoException (util.js:1022:11)
at _exceptionWithHostPort (util.js:1044:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1198:14)
code: 'ECONNREFUSED',
errno: 'ECONNREFUSED',
syscall: 'connect',
address: '127.0.0.1',
port: 80,
config:{......................
.............................
.........}
I don't know what is wrong in my node js app. I am posting data to port 80(instead of to localhost' port) Does someone have any ideas?
Since we updated from Node 0.8 to Node 0.10 we're seeing these errors:
{ [Error: read ECONNRESET] code: 'ECONNRESET', errno: 'ECONNRESET',
syscall: 'read' }
Error: read ECONNRESET
at errnoException (net.js:878:11)
at TCP.onread (net.js:539:19)
I know this error was ignored before 0.10, but I'd like to know
what's causing this and how I can fix it/debug it?
Is it a problem on our end (server) closing connections too soon?