fly wireguard remove fails (incorrect key size: 33)

Open
#3,378 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
go
Domain
cli, networking

Research direction

Start by reproducing fly wireguard remove for the malformed peer described in the report, then trace the removal path and how the server's key-size error is handled. Done means the malformed peer can be removed or the command returns a clear, non-500 error instead of the unhandled upstream failure.

Written by the indexing model from the issue text.

Description

bug

Describe the bug
I was in the process of creating a Wireguard peer via GraphQL API. By mistake, I created a peer with a wrong key, and now fly wireguard remove is unable to remove it:

Error: server returned a non-200 status code: 500
Error: unhandled upstream service error: nats wg delete: delete peer: delete peer
aaaa1234 from kernel: pubkey parse error: wgtypes: incorrect key size: 33
  • Operating system: Alpine Linux 3.19.1
  • fly version flyctl v0.2.20 linux/amd64 Commit: 79d5a83e7d73d0a200f0cc9201822db4f1fdb91a BuildDate: 2024-03-15T21:31:19Z
Dominant language
Go
Stars
1.7k
Forks
311
Avg merge
12h 50m
Merged PRs (30d)
78

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from superfly/flyctl

All issues in superfly/flyctl

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.