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.

Sign up for GitHub

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

Jump to bottom

v5.4,v5.5 Message sometimes wrong when upstream connection fails #712

Closed
philipianpearce opened this issue Dec 7, 2021 · 1 comment
Closed

v5.4,v5.5 Message sometimes wrong when upstream connection fails #712

philipianpearce opened this issue Dec 7, 2021 · 1 comment
Assignees
@philipianpearce
Labels
bug fixed

Comments

@philipianpearce
Copy link
Contributor

v5.4,v5.5 Message to user and in logs is sometimes wrong when upstream connection fails. The e2g status number is correct in logs but message does not correspond and category set (should be blank on connection failure)
@philipianpearce philipianpearce self-assigned this Dec 7, 2021
philipianpearce added a commit that referenced this issue Dec 7, 2021
@philipianpearce
Fix bug #712 - Upstream connect failure message wrong
05c195a
philipianpearce added a commit that referenced this issue Dec 21, 2021
@philipianpearce
Fix bug #712 plus other changes
9a1187c
philipianpearce added a commit that referenced this issue Dec 21, 2021
@philipianpearce
Squashed commit of the following:
d65093e 
    Major changes to socket and tunnel code to fix bug #714

    update doc on dockermode

    Fix bug #712 - message wrong when upstream connection fails

    Other minor fixes.
@philipianpearce
Copy link
Contributor Author

Fixed in v5.4 and v5.5dev

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@philipianpearce philipianpearce

Labels
bug fixed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@philipianpearce