Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Attempt to automatically fix wireguard issues #3306

Open
benbjohnson opened this issue Feb 16, 2024 · 0 comments
Open

Attempt to automatically fix wireguard issues #3306

benbjohnson opened this issue Feb 16, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@benbjohnson
Copy link
Contributor

benbjohnson commented Feb 16, 2024

When encountering a Wireguard error, the user is sometimes required to restart the agent or run fly wg reset.

Errors can look like:

Pinging WireGuard gateway (give us a sec)... FAILED
(Error: ping gateway: no response from gateway received)

We can't establish connectivity with WireGuard for your personal organization.

or

Error: tunnel unavailable: failed probing "<app-name>": context deadline exceeded

The CLI should automatically try to recover from the error and try again so that users don't have to waste time debugging Wireguard issues when there is a simple fix.

@benbjohnson benbjohnson added the bug Something isn't working label Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant