Stuck on an issue?

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.

Connection reset error stops spark after some time?

See original GitHub issue

From my logs (stdout & stderr of spark). This has happened several times. spark-wallet --version == 0.1.1.

...
GET /stream?access-key=RAviKLwv5ZZBLUDngcBiagM7cLdPv923iSy6MdrVdus 200 25.565 ms - -
POST /rpc 200 13.431 ms - 411
uncaughtException, stopping process
Error: read ECONNRESET
    at _errnoException (util.js:1022:11)
    at TCP.onread (net.js:628:25)

Issue Analytics

State:
Created 5 years ago
Comments:13 (7 by maintainers)

Top GitHub Comments

1reaction

ghostcommented, Sep 25, 2018

My conclusion is that the issue has been solved. Tried all kinds of stuff and sometimes I see a connection warning on the phone but the process on the server keeps going. Nice and thanks a lot!

1reaction

shesekcommented, Sep 23, 2018

@darosior Thanks! That’s very helpful, I am able to reproduce with that.

It looks like this is related to the changes introduced in https://github.com/shesek/spark-wallet/commit/62798caf243415d4194d5dc6b6e7bf388bb00d02. Removing the use of createMultiServer appears to fix the issue:

diff --git a/src/transport/tls.js b/src/transport/tls.js
index 3b8f1e5..874dc18 100644
--- a/src/transport/tls.js
+++ b/src/transport/tls.js
@@ -10,7 +11,8 @@ const defaultDir = path.join(require('os').homedir(), '.spark-wallet', 'tls')
 
 module.exports = (app, name=app.settings.host, dir=defaultDir, leEmail) => {
   const tlsOpt = leEmail ? letsencrypt(name, dir, leEmail) : selfsigned(name, dir)
       , redir  = (req, res) => (res.writeHead(301, { Location: `https://${ req.headers.host || name }/` }), res.end())
-      , server = createMultiServer(tlsOpt, app, redir)
+      , server = https.createServer(tlsOpt, app)

I knew from the beginning that createMultiServer is quite hacky and error-prone, and it has already caused issues previously (#10), so I think I’m just going to remove it. This means that users trying to access a TLS-enabled Spark server without using https:// will receive a connection error (instead of a 301 redirection), but I think that might be better than continuing to maintain this hack. :-\