On reverse tunnel reconnect, handle existing listen
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 16.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
When the connection goes bad for the websocket, it doesn't fail for quite a while, seems like 10 minutes or so.
Can we configure WS keepalives to make it recover from that faster?
Also, when auto-reconnecting if the old connetion is still not closed, it bails with an error message saying that the port is already listening on the server side... it would be nice if auto reconnecting sitll worked even if you have reverse tunnels
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the websocket reconnect path and the reverse-tunnel handling for an existing server-side listener. Check how WS keepalives are configured and how reconnect errors are handled when the old connection has not closed. Done means broken websocket connections recover faster and reverse tunnels reconnect without a port-already-listening failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100