You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently upgraded my Docker image to use the latest commit on the master branch of Smokescreen (c86310d).
Right after a connection is allowed through the proxy, I'm occasionally seeing this error log message Failed to connect to remote host: <nil> but of course <nil> doesn't contain any helpful information.
It seems like this problem might be related to the recent change in #194?
I'm not very experienced with Go but reading the code, I'm not sure how e.Error() is returning nil.
The text was updated successfully, but these errors were encountered:
Hello! Sorry for the delay on this and thanks for reporting! We actually noticed this internally too, and I dug through all the parts of the code were we pass down that error but didn't find anything suspicious :/ When we saw the issue, we were able to reproduce intermittent connection refused errors to the destination with netcat, so I think there actually was some sort of error, but we haven't been able to figure out why it's unwrapping incorrectly. I don't think#194 caused this since that error string ("Failed to connect to remote host: " is coming from the else case and we only added an extra else if in that PR.
I'll leave this open for now for us to keep digging into, but just wanted to let you know we're aware and equally confused!
I recently upgraded my Docker image to use the latest commit on the
master
branch of Smokescreen (c86310d).Right after a connection is allowed through the proxy, I'm occasionally seeing this error log message
Failed to connect to remote host: <nil>
but of course<nil>
doesn't contain any helpful information.It seems like this problem might be related to the recent change in #194?
I'm not very experienced with Go but reading the code, I'm not sure how
e.Error()
is returning nil.The text was updated successfully, but these errors were encountered: