uncaught error in RtcToNet from core.tcpsocket.connect

Question

I've had Simple SOCKS running since yesterday (~18 hours) and I saw this weird error in the log:

Uncaught (in promise) Object {errcode: "NAME_NOT_RESOLVED", message: "Chrome Connection Failed: NAME_NOT_RESOLVED net::ERR_NAME_NOT_RESOLVED"}

The reported location is unhelpful: (program):1

That error comes from freedom-for-chrome: https://github.com/freedomjs/freedom-for-chrome/blob/master/providers/core.tcpsocket.js#L57

That's in connect so my guess is this is RtcToNet not catching the error. The proxy seems fine, BTW, it's just that uncaught errors are a little worrying.

该提问来源于开源项目：UWNetworksLab/uProxy-p2p

Answer 1

So, after ~18 hours of Simple SOCKS-age, something related to this seems to have killed my proxy. I see this uncaught error:

Uncaught (in promise) closed

Again, it comes from (program):1. Very helpful!