Auto-recovery that knows when a restart cannot help and stops repeating itself, a fix for qBittorrent quietly listening on the wrong address after a VPN reconnect, clearer reporting of what recovery is waiting for, and a checksum on updates installed from inside the app.
New Features
- Port forwarding that is switched off no longer restarts your VPN - when your VPN reports that port forwarding is turned off in its own settings, or that the server region you are connected to does not offer it, qbPortWeaver now says so in the log and waits for you to change it; it used to treat that the same as a VPN fault and restart your VPN to try to fix it, again and again on a timer, which could never work and briefly dropped your connection every time; this mainly affected PIA, the provider that reports the reason clearly enough to tell the two apart
- qBittorrent is nudged back into listening after a VPN reconnect - when a VPN reconnects the adapter usually keeps its name but is given a new address, and qBittorrent can be left listening on the previous one, so everything looks healthy from the outside while nobody can actually connect to you; if the forwarded port stops answering after an address change, qbPortWeaver now nudges qBittorrent into listening again before trying anything heavier like restarting your VPN, and your qBittorrent settings are left exactly as you had them; it also corrects an address that no longer exists as soon as it sees one
- Auto-recovery stops repeating itself - auto-recovery restarts your VPN when it stops providing a working forwarded port, and if three restarts in a row do not produce one it now stops and says so in the log rather than carrying on indefinitely; it starts again by itself the moment a port comes through, and a recovery you run yourself with the Test button is never held back
- Auto-recovery says what it is doing - the Status window's Auto-recovery line now covers both of its triggers, repeated failed cycles and a forwarded port that stays closed, so a closed port counting toward a recovery is visible instead of silent; it reads Disabled only when you have switched both triggers off, where before it could say Disabled while the app could still restart your VPN; and the warning that repeats while a port stays closed now says the recovery has already run and what it is waiting for
- Updates are checked before they are installed - when you install an update from inside the app, the downloaded installer is now checked against the checksum published with the release before it is run; if it does not match, the file is deleted and the release page opens instead, so a download that arrived damaged or incomplete is never launched
- Problems that used to fail quietly now say so - the log file being impossible to write to, the Windows startup entry not being updated after the app moved, the recent port changes list failing to save, or an older helper service left behind by an upgrade; each of these now reports itself, and the log one arrives as a tray message since by definition it cannot be written to the log
- Nicotine+ plugin updates are offered when the plugin changes - Settings used to decide whether a plugin update was available by comparing version numbers, and the plugin's version follows the app's, so a fix to the plugin alone was never offered unless the app version happened to move as well; it now compares the installed files with the ones this build carries, so an update is offered whenever there is genuinely something new to install
- Multi-line log entries stay together - a log entry can run to more than one line, and the Log Viewer now keeps those lines with the entry they belong to, so filtering by level, subsystem or time range never shows part of an entry on its own or leaves a stray line sitting under an unrelated one
- The next-sync countdown is accurate after a slow cycle - the Status window used to start its countdown from the moment a cycle began rather than the moment it finished, so after a slow cycle, one that restarted your client or ran a recovery, it could sit on Due now for a minute or two before anything actually happened; it now counts down to the real time
- Your network adapter is always switched back on - the kind of auto-recovery that switches your network adapter off and straight back on could still leave it off if Windows shut down or the app was stopped in the moment between the two, and it stayed that way after a restart; it is now always switched back on whatever interrupts the recovery, which matters for NAT-PMP setups using a router or gateway rather than ProtonVPN or PIA
Full Changelog: v2.6.6...v2.6.7