Skip to main content

Recent releases

View All
Quarterly
Voyager

26.8.6 ‘Voyager’ released

· 5 min read

Changes compared to 26.8.5

Enhancements​

  • Updated the Comet Management Console API to now report details about invalid parameters in many cases (COMET-60493)

Bug Fixes​

  • Fixed an issue where a Windows backup job could fail with an unhelpful "basic_string: construction from null is not valid" message when a third-party VSS provider reported a successful snapshot without a device object. The error now names the VSS call and the provider involved
  • Fixed an issue where a custom known_hosts file path configured for a Proxmox Protected Item was discarded when the Protected Item was saved again, in both the Comet Backup desktop app and the Comet Management Console (COMET-60593)
  • Added the missing host-key verification options when editing a Proxmox Protected Item in the Comet Management Console, matching the options already available in the Restore dialog. Previously the Comet Management Console had no control for these and would reset host-key verification to "Allow any host key" on save (COMET-60593)
  • Fixed an issue where editing a Proxmox Protected Item in the Comet Management Console would discard its exclusion list, and reset its backup method and Changed Block Tracking setting, if the device was offline or the connection test had failed (COMET-60593)
  • Fixed an issue where Proxmox disks numbered 10 and above were silently excluded from a backup job when the Protected Item was configured in the Comet Management Console (COMET-60593)
  • Fixed an issue with the Comet Backup desktop app crashing when opening a Proxmox Protected Item if one of its selected disks had been detached from the guest since the Protected Item was last saved (COMET-60593)
  • Fixed an issue where an SSH private key entered when editing a Proxmox Protected Item in the Comet Management Console was discarded on save, and where a Proxmox Protected Item using private key authentication could not be saved or have its connection tested at all. The Private key field is now a multi-line box, so a pasted key keeps its line breaks instead of being flattened into an unusable single line (COMET-60593)
  • Fixed an issue where editing a Proxmox Protected Item in the Comet Management Console while the device was offline discarded changes to the SSH server address, username, password and authentication mode (COMET-60593)
  • Fixed an issue where the Password and Private key fields shown when editing a Proxmox Protected Item in the Comet Management Console did not match the saved authentication mode until the mode was changed by hand (COMET-60593)
  • Added validation preventing a Proxmox Protected Item from being saved with custom host key verification selected but no known_hosts file path entered, which previously caused every backup job for that Protected Item to fail (COMET-60593)
  • Fixed an issue with saving SSH usernames for a Proxmox Protected Item when using Private key authentication in the Comet Backup desktop app (COMET-60592)
  • Fixed a connection leak in the backup client: an HTTP error response from the server left the response body unclosed, so a repeatedly failing job log upload leaked one connection per retry attempt (COMET-60468)
  • Fixed the Comet Backup desktop app crashing when submitting a new password during sign-in for accounts with "Require user to change password at next login" enabled, which left the account stuck repeating the password-change prompt (regression in 26.5.3) (COMET-60312)
  • Fixed an issue in the Comet Management Console where dismissing the Getting Started guide could leave blank space reserved down the right-hand side of the page until the next page load (COMET-60581)
  • Fixed an issue causing "Couldn't look up properties of" errors in the Comet Server log when multiple operations occur simultaneously against a single Storage Vault stored in the Comet Server Storage Role (COMET-995)
  • Fixed an issue causing "Server already received a more recent progress update, back off" errors in the Comet Server log for backup jobs finishing at particular times (COMET-995)
  • Fixed an issue where a backup job could be incorrectly shown as running again after it had already finished (COMET-995)
  • Fixed an issue it shows a false no files restored when doing a simulate restore for o365 (COMET-60462)
  • Fixed an issue with restoring to original location, that could cause files to save to the wrong location (COMET-60402)
  • Fixed an issue where the Getting Started guide could block clicks on buttons near the right-hand edge of the page in the Comet Management Console on narrower browser windows (COMET-60574)
  • Fixed an issue where the Synology package for DSM 7 would install but could not be started if the branded product name conflicted with DSM service name limitations by using characters other than letters, digits, and the characters ., _, and -. NOTICE: for affected branding only, DSM 7 treats the fixed package as a new installation rather than an upgrade — the old non-starting package remains in Package Center and should be uninstalled manually (COMET-60408)
  • Fixed an issue with handling network or server outages on FTP, WebDAV, Storj, and Spanned storage targets (COMET-60520)