fix(gRPC): improve handling device pubkey change#1703
Merged
wojcik91 merged 4 commits intorelease/1.6-alphafrom Nov 13, 2025
Merged
fix(gRPC): improve handling device pubkey change#1703wojcik91 merged 4 commits intorelease/1.6-alphafrom
wojcik91 merged 4 commits intorelease/1.6-alphafrom
Conversation
moubctez
approved these changes
Nov 13, 2025
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
2 participants
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.
Changing device pubkey would lead to the stats handling thread panicking. This in turn would cause a reconnect from the gateway side, unnecessarily interrupting VPN sessions.
Currently this situation causes duplicate "VPN Client Connected" events to be emitted, but I decided against fixing this since we'll soon be refactoring our whole approach to VPN client connections (#1701).
Resolves #1671