fix: socks5 proxy rejected connection - failure #2
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.
Fixes rehanvdm/tailscale-lambda-extension#4
This error:
Error: Socks5 proxy rejected connection - Failurecan happen during a cold start or a normal function call of the lambda. I believe that even though the tailscale process is running, the socks5 proxy has not fully initialized. This is more likely to happen on cold starts, it might also have to do with several logins to the tailscale networks at once.In my tests only 1 retry attempt was needed, the 10ms delay was enough. We might be able to go lower, but I have not tested it. If we could go as low as 1ms or 0ms, it might mean the first request wakes something up/resets something, just a hunch. For now, I'm happy with a 10ms retry whenever this intermittent error happens.