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

Close leaky directClient #6297

Merged
merged 1 commit into from
Apr 2, 2021
Merged

Conversation

Joerger
Copy link
Contributor

@Joerger Joerger commented Apr 2, 2021

Fixes #6291

@Joerger Joerger requested a review from awly April 2, 2021 20:03
@Joerger Joerger changed the title Close leaky direct client Close leaky directClient Apr 2, 2021
@Joerger Joerger force-pushed the joerger/fix/close-failed-direct-client branch from 0ff5d59 to c148f77 Compare April 2, 2021 20:05
Copy link
Collaborator

@r0mant r0mant left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Joerger Nice catch!

@Joerger Joerger force-pushed the joerger/fix/close-failed-direct-client branch from c148f77 to ab2ca0f Compare April 2, 2021 20:51
@Joerger Joerger enabled auto-merge (squash) April 2, 2021 20:51
@Joerger Joerger merged commit 8ecbefb into master Apr 2, 2021
@Joerger Joerger deleted the joerger/fix/close-failed-direct-client branch April 2, 2021 21:04
Joerger added a commit that referenced this pull request Apr 2, 2021
Joerger added a commit that referenced this pull request Apr 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

"remote error: tls: bad certificate" when connecting service through tunnel
3 participants