I am trying to run 'dcl start' command from the terminal. The Decentraland Preview webpage opens and terminal says 'Acquring comms connection'. But after that it gives the error below:
Oops, it seems the catalyst isn't working well. [HPM] Error occurred while proxying request 127.0.0.1:8000/lambdas/collections/wearables?collectionId=urn:decentraland:off-chain:base-avatars to https://peer.decentraland.org/ [ECONNRESET] (https://nodejs.org/api/errors.html#errors_common_system_errors) Oops, it seems the catalyst isn't working well. [HPM] Error occurred while proxying request 127.0.0.1:8000/lambdas/collections/wearables?wearableId=urn:decentraland:off-chain:base-avatars:elegant_striped_shirt&wearableId=urn:decentraland:off-chain:base-avatars:elegant_blue_trousers&wearableId=urn:decentraland:off-chain:base-avatars:f_m_sandals&wearableId=urn:decentraland:off-chain:base-avatars:modern_hair&wearableId=urn:decentraland:off-chain:base-avatars:f_mouth_04 to https://peer.decentraland.org/ [ECONNRESET] (https://nodejs.org/api/errors.html#errors_common_system_errors) [HPM] ECONNRESET: Error: socket hang up at connResetException (node:internal/errors:704:14) at TLSSocket.socketOnEnd (node:_http_client:505:23) at TLSSocket.emit (node:events:525:35) at endReadableNT (node:internal/streams/readable:1358:12) at processTicksAndRejections (node:internal/process/task_queues:83:21) { code: 'ECONNRESET' }
What could cause this error ?
Related
[HPM] ECONNRESET: Error: socket hang up at connResetException (internal/errors.js:610:14) at Socket.socketCloseListener (_http_client.js:400:25) at Socket. Emit (events.js:327:22) at TCP.<anonymous> (net.js:674:12) { code: 'ECONNRESET'
after doing npm start and the UI is running but I'm getting this data while the page is loading.
so i'm having this problem on a nuxt implementation with vercel, at random moments the site doesn't load and throws a 502 http error
this is the stacktrace of vercel:
ERROR Unhandled Promise Rejection {"errorType":"Runtime.UnhandledPromiseRejection","errorMessage":"FetchError: request to {api_url} failed, reason: Client network socket disconnected before secure TLS connection was established","reason":{"errorType":"FetchError","errorMessage":"request to {api_url} failed, reason: Client network socket disconnected before secure TLS connection was established","code":"ECONNRESET","message":"request to {api_url} failed, reason: Client network socket disconnected before secure TLS connection was established","type":"system","errno":"ECONNRESET","stack":["FetchError: request to {api_url} failed, reason: Client network socket disconnected before secure TLS connection was established"," at ClientRequest.<anonymous> (server.js:16011:11)"," at ClientRequest.emit (events.js:315:20)"," at ClientRequest.EventEmitter.emit (domain.js:483:12)"," at TLSSocket.socketErrorListener (_http_client.js:426:9)"," at TLSSocket.emit (events.js:315:20)"," at TLSSocket.EventEmitter.emit (domain.js:483:12)"," at emitErrorNT (internal/streams/destroy.js:92:8)"," at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)"," at processTicksAndRejections (internal/process/task_queues.js:84:21)"]},"promise":{},"stack":["Runtime.UnhandledPromiseRejection: FetchError: request to {api_url} failed, reason: Client network socket disconnected before secure TLS connection was established"," at process.<anonymous> (/var/runtime/index.js:35:15)"," at process.emit (events.js:327:22)"," at process.EventEmitter.emit (domain.js:483:12)"," at processEmit [as emit] (/var/task/node_modules/signal-exit/index.js:161:32)"," at processPromiseRejections (internal/process/promises.js:209:33)"," at processTicksAndRejections (internal/process/task_queues.js:98:32)"]}
Unknown application error occurred
So the error it's about a connection with the api, for what i found this is a Node error but my api is developed on Laravel so i'm really lost
Thanks for the help
I ran into this issue (with a Next.js project on Vercel) and fixed it. I was calling an external API but forgot to await one of the handlers, so the Lambda eventually stopped waiting for the API call response once my code finished running.
I'm trying issue a post to a soap web service at following url https://xxx.xxx.gov.ar/AntecedentesService/AntecedentesService.asmx and I get the following error:
Error: Client network socket disconnected before secure TLS connection was established
at TLSSocket.onConnectEnd (_tls_wrap.js:1088:19)
at Object.onceWrapper (events.js:277:13)
at TLSSocket.emit (events.js:194:15)
at endReadableNT (_stream_readable.js:1125:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
code: 'ECONNRESET',
path: null,
host: 'xxx.xxx.gov.ar',
port: 443,
If I issue a post with curl like this:
curl -X POST -H "Content-Type: text/xml" -d #request01.xml https://xxx.xxx.gov.ar/AntecedentesService/AntecedentesService.asmx
it works ok. If I try to access it from vscode using the rest client plugin I get exaclty the same error, so I guess it could be a problem with node.
Just to dismiss axios, I also tried with https.request following this example, and I get the same error
Any idea how to solve it?
I'm using node v10.15.3 and axios 0.18.0 from Linux pop-os 4.15.0-48-generic
I'm developing an AngularJS 1.7.x application (started 3 years ago), and when I started Gulp was the tool to use.
Yesterday, when I resume my work on my app, I suddenly get a crash on the first XHR request.
So I run "gulp serve", it opens chrome with the login page, everything is loading correctly, and then, I click the login button, which issue a REST call to my PHP Backend (served by Apache/2.4.37 (Unix) PHP/7.2.14)
The package.json of my project didn't changed in quite some time.
I've recently updated npm (6.9.0) & node (8.11.1), but it's not that recent.
[12:14:13] Starting 'serve'...
[HPM] Proxy created: /rest -> http://localhost/
[12:14:13] Finished 'serve' after 49 ms
[BrowserSync SPA] Running...
[Browsersync] Access URLs:
--------------------------------------
Local: http://localhost:3000/
External: http://192.168.1.21:3000/
--------------------------------------
UI: http://localhost:3001
UI External: http://localhost:3001
--------------------------------------
[Browsersync] Serving files from: .tmp/serve
[Browsersync] Serving files from: src
[HPM] Error occurred while trying to proxy request /rest/authenticate from localhost:3000 to http://localhost/ (HPE_INVALID_CONSTANT) (https://nodejs.org/api/errors.html#errors_common_system_errors)
events.js:183
throw er; // Unhandled 'error' event
^
Error: write after end
at write_ (_http_outgoing.js:622:15)
at ServerResponse.write (_http_outgoing.js:617:10)
at IncomingMessage.ondata (_stream_readable.js:639:20)
at emitOne (events.js:116:13)
at IncomingMessage.emit (events.js:211:7)
at IncomingMessage.Readable.read (_stream_readable.js:475:10)
at flow (_stream_readable.js:846:34)
at resume_ (_stream_readable.js:828:3)
at _combinedTickCallback (internal/process/next_tick.js:138:11)
at process._tickCallback (internal/process/next_tick.js:180:9)
In my php Backend, my configuration file was giving an empty "ReCaptcha" secret, which end up producing this crash on gulp/proxy...
Can't understand why the error thrown by ReCaptcha can mess up the proxy so much...
I have 2 nodejs modules that communicate via HTTPS.
In very rare occasions, one of the requests to the server module returns:
Stack Trace
Error: socket hang up
at TLSSocket.onHangUp (_tls_wrap.js:1049:19)
at TLSSocket.g (events.js:260:16)
at emitNone (events.js:72:20)
at TLSSocket.emit (events.js:166:7)
at endReadableNT (_stream_readable.js:913:12)
at nextTickCallbackWith2Args (node.js:442:9)
at process._tickDomainCallback (node.js:397:17)
with errno set to ECONNRESET
Is there any reason why something like that would happen?
I already checked for:
Server crashes before responding
Server response takes too long
certificate expired.
Also, the server logs do not show any kind of problem.
Thanks
ECONNRESET (Connection reset by peer): A connection was forcibly closed by a peer. This normally results from a loss of the connection on the remote socket due to a timeout or reboot. Commonly encountered via the http and net modules.
"Common System Errors" : https://nodejs.org/api/errors.html
so try first to see what's happen
process.on("uncaughtException", function (err) {
console.log('err uncaught Exception : ', err);
})