Hello everyone,
I’m running the CipherMail Community Edition Virtual Appliance and would like to update it to the latest release. What is the recommended upgrade path?
Hello everyone,
I’m running the CipherMail Community Edition Virtual Appliance and would like to update it to the latest release. What is the recommended upgrade path?
CipherMail Gateway version 6 is a major redesign. Databases from earlier versions cannot be imported into version 6. You can export all certificates and PGP keys from your current gateway to a file and import that file into the new gateway.
If you have a paid support contract and need help upgrading to version 6, please contact our support team.
If you want to upgrade an existing version 6 appliance to a newer release, the steps depend on your edition:
Hi,
thank you for the clarification — I appreciate the detailed information.
I’m currently running CipherMail Gateway version 6.22 (Community Edition) and would like to upgrade to the latest release, 6.25. Since I’m already on version 6, I assume this is a minor update and not a major version migration.
Could you please confirm the recommended upgrade path for upgrading from 6.22 to 6.25 on the Community Edition?
As mentioned, I understand that for v6.x updates, the CE uses RPM packages — so I’d like to know:
Where to download the latest RPMs
Whether there are any pre-update steps (e.g., backup, service stop)
Updating the VM for the enterprise edition:
From the command line:
sudo dnf update
Updating the VM for the community edition:
Check changelog (CHANGELOG.md · main · CipherMail B.V. / ciphermail-community-gateway · GitLab) for any update notes
Download the latest RPMs (5) from Releases · CipherMail B.V. / ciphermail-community-gateway · GitLab
Copy the RPMs to the VM using scp or the Cockpit file browser (Cockpit — CipherMail Documentation)
Open the command line on the VM (with ssh, or use the Cockpit terminal [Cockpit — CipherMail Documentation])
Then from the command line, run:
sudo dnf install *.rpm
Restart the gateway
sudo systemctl restart ciphermail-backend
sudo systemctl restart ciphermail-portal-backend
Check backend startup logs:
sudo journalctl -u ciphermail-backend -f
sudo journalctl -u ciphermail-portal-backend -f