-
-
Notifications
You must be signed in to change notification settings - Fork 140
Transport endpoint is not connected (os error 107) #1288
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
Comments
Could you please run Warpgate with |
Will do! It may take a few days/weeks for it to occur, as a heads up. |
Hi there! I am experiencing the same error. I have set RUST_LOG=debug in the environment variables for the Docker container. Here are the log messages before the error occurs:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey! Thanks again for this great project :)
We're unfortunately semi-regularly encountering an issue where Warpgate starts refusing all SSH traffic. We have to access the server and restart the Docker container for it to come back online. This is all we see in the logs:
I left the first few lines in in case they're useful, but they're just the tail end of the normal barrage of login attempts from attackers. As you can see, there's nothing in the logs from that point until we restart the container. It would be incredibly helpful to both understand what's going wrong, but also if the process could hard exit so that the container would automatically restart.
Let me know if I can provide any further details!
The text was updated successfully, but these errors were encountered: