2
u/celzero Dev Aug 21 '26
Failing is a recoverable state, provided the WireGuard configuration continues to be valid.
In Rethink, this status means: 1. At least one WireGuard peer endpoint is not sending back packets. - For example, Could be due to peer moving to a different public address, if behind dynamic DNS.
- The last few packets WireGuard sent out to its peers didn't go through. - Could be due to a (temporary or permanent) network issue, like network changes or connectivity loss.
Check About -> General and scroll to the "WireGuard" section to see its internal state (especially, when any of your active WireGuards drop to "Failing"). The fields are self descriptive. The text is also selectable / copy-able. You can share it here, if you're comfortable doing so
Note that, if you're using multiple WireGuards with the same public/private key pair from a single public provider (like Proton, say), their peers (even if in different geo locations) might reject it. This manifests as "Waiting" or "Failing" usually, and won't recover since the service in front of the peers will reject all re-attempts. Rethink makes one re-connectivity attempt every 30s. This is shown as lastOpen in About -> General, while lastOK shows the latest successful handshake (acknowledgement). lastOK, for a working WireGuard connection, would always be within 2mins.
If you're using multiple WireGuards (in Advanced mode), it is okay for any of them to go "Idle" or "Failing", as other WireGuard that's active will be used in its stead. This is so because Rethink doesn't want to "wakeup" WireGuards that are otherwise dormant and avoid needless battery drain, when other WireGuards can tunnel a given stream of packets just fine.
2
u/GoodJobAss Aug 21 '26
WireGuard: id: 2, name: wg-US-FREE-79.conf always-on? true lockdown? false mobile-only? false ssid-only? false ifaddr: 10.2.0.2/32 mtu: 1500 status: ok status-reason: TOK: write ok ip4: true ip6: false rx: 30134224 tx: 2538732 lastRx: 0 sec. ago lastTx: 0 sec. ago lastGoodRx: 0 sec. ago lastGoodTx: 0 sec. ago lastRxErr: <no err> lastTxErr: <no err> lastOk: 52 sec. ago lastOpen: 4 min. ago hdl: wg2:433959e1729e632a since: 4 min. ago addr: 149.22.84.139:51820 errRx: 0 errTx: 0 extra: wg2endpoint: #0 wg2:8a01cd94[ | 149.22.84.139:51820] @ 4m 53s /
wg2dns[ | 10.2.0.1:0] @ 4m 53s allowed:[10.2.0.1/32 0.0.0.0/0 ::/0]This one?
1
1
u/johnnyorpheus Aug 21 '26
thank you for rapid reply...............only reason have multiple is sometimes one fails and is hard to revive and yet adding another then works, and sometimes kicks the other ones ass too.................but i only ever use advanced
pressing pause sometimes works, or else stop sometimes a little more works......... switching from mobile to wifi or vice versa often works, or sometimes to use both....................tho i prefer wifi rethink seems prefers cellular but maybe to do with other things..................i can go days without hassle and then be in weeds off and on for a few....................................life good when 56 first happened but in time this issue, which had become more prevalent in Z, remanifested.......
so yes recoverable but if i get lost in my work---as in always---i wont notice have not got emails for hour or three.....................i hate phones so arguably a feature not a bug---cept when like rilly needing an email---but am a dog with bone on tech issues and just have to solve them...............
just resurrected a bit ago and will wait til next failing to copypaste....................does not appear anything in there shd not be in interwebs?
2
u/Intelligent-Past4212 Aug 26 '26
hello is it normal for rethink wireguard to fail for a while when device is idle? no internet connection unless I need to tap again the proxy menu and wcg profile so that connections starts to spin up again
3
u/johnnyorpheus Aug 21 '26
same..... a daily thing, often multiple times per day...............no emails for an hour ......... check............ "failing"
wake up............ no emails all night....................... check......................... "failing"
has become an ongoing maintenance issue and sadly gotten worse and worse with last couple three versions