Conversation
Ping both sides every 12s, fail a missing pong in 45s, refresh a 60s read deadline on every frame, tighten TCP keepalive to 15s, and reconnect the relay from 500ms up to 10s with an explicit drop reason. Co-authored-by: Daniel <znsoft@163.com>
znsoftm
marked this pull request as ready for review
September 14, 2026 20:06
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Idle public tunnels were dying after hours with
{"ok":false,"error":"search backend offline","code":"offline"}because NAT / a 90sReadDeadlineclosed the link even though the relay already reconnects.Both ends now keep the TCP path warm and fail dead sessions faster:
KeepAliveConfig+SetKeepAlivePeriod) and on the accepted proxy connmissing pong,read idle timeout, etc.)Shared helpers live in
internal/tunnelwith tests for deadline refresh, pong timeout, backoff, and proxy ping emit/answer.