Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Failed to connect to remote host: <nil>" error log #202

Open
jportner opened this issue Aug 17, 2023 · 2 comments
Open

"Failed to connect to remote host: <nil>" error log #202

jportner opened this issue Aug 17, 2023 · 2 comments

Comments

@jportner
Copy link

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.

@jjiang-stripe
Copy link
Collaborator

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!

@jportner
Copy link
Author

Thank you for the update!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants