aboutsummaryrefslogtreecommitdiff
path: root/tests/safe-rm-rf
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-07-05 16:35:09 -0400
committerCraig Jennings <c@cjennings.net>2026-07-05 16:35:09 -0400
commitfe4383bfc0e76f7f1948716aa8b2bc542d712634 (patch)
tree3135c88d77be485980de606ebb34b34a3159ffff /tests/safe-rm-rf
parent8cdf3cbda9fd5eeab0f91571eda1872594a86af7 (diff)
downloadarchsetup-fe4383bfc0e76f7f1948716aa8b2bc542d712634.tar.gz
archsetup-fe4383bfc0e76f7f1948716aa8b2bc542d712634.zip
fix(wireguard): replace dead Proton configs with a working set
The seven Proton configs imported April 10 completed the WireGuard handshake but Proton routed no data: DNS and traffic through the tunnel timed out on every server. Fresh configs from the Proton dashboard route data normally. That confirms the old keys were deauthorized account-side, not a local routing, firewall, or NetworkManager fault. Swap in three fresh configs (NL, US-CA, US-TX) and point the panel tunnels manual-test at the new connection names.
Diffstat (limited to 'tests/safe-rm-rf')
0 files changed, 0 insertions, 0 deletions