VALT 6.7.9-2

November 2nd, 2026

Technical

• VALT Menu
  • Added a Support Tools menu to generate a support report for IVS Support to run the IVS data collector
  • Added the server name, server type, VALT version, and IP address to the main menu and to the top of every screen
  • Added a warning to the main menu when the running VALT containers do not match the installed package version or are not running
  • Updated the VALT Menu to restart into the new version after a package upgrade, including an idle VALT Menu on the server console
  • Updated Ctrl-C to return to the main menu instead of closing the VALT Menu
  • Updated Network Settings > Apply Network Config to ask for confirmation, check the configuration for errors, and roll back automatically unless the change is kept within 120 seconds
  • Fixed issue where cancelling the network interface selection configured the last interface in the list
  • Fixed issue where pressing Esc when choosing Static or DHCP configured the interface for DHCP
  • Fixed issue where Configure VALT > Enter VALT Prod Mode still offered to switch modes and rebuild VALT on a Media Server after reporting that no changes were made
  • Fixed issue where Import CA Certificate opened its file browser in a folder that does not exist
  • Fixed issue where the details of an existing network bond or VLAN showed repeated lines
  • Fixed issue where a failed container restart showed no error
• Network Configuration
  • Updated the ivs-valt-appliance package to rename the default '50-cloud-init.yaml' netplan configuration to 'valt.yaml', as it already does for '00-installer-config.yaml'
  • Updated '/etc/netplan/valt.yaml' to be readable by root only, as netplan requires
  • Updated Network Settings in the VALT Menu to rename the default netplan configuration to 'valt.yaml' when 'valt.yaml' is missing
• Server Configuration
  • Media Servers whose App Server address is the same server now skip the SSH key exchange and the App Server database update, and show a warning
  • Added a message before Media Server configuration asks for the App Server's ivsadmin password
  • Fixed issue where Media Server configuration asked for an SSH password when its SSH keys were not set up
  • Fixed issue where configuring a Media or Warm Standby Server showed a "cannot touch" error
  • Fixed issue where the active recordings check showed connection output when Wowza was not reachable
  • Fixed issue where the Warm Standby SSH key setup did not ask for a server address when none was set