Before you begin:
If the upgrade fails, it may not be possible to recover your data. Take a VM snapshot or backup of your server before proceeding.
What Is Being Upgraded?
Tomcat is upgraded from version 9 to 10
Java - is upgraded to version 21 (Java 17 for AWS deployments)
PostgreSQL - is upgraded from version 13 to 16.
Upgrading Tomcat and Java
Tomcat and Java are upgraded as part of the standard upgrade process. Follow the Upgrading the Faddom Server guide to complete this step.
AWS deployments: Java will be upgraded to version 17 instead of 21. No additional steps are required.
Upgrading PostgreSQL
PostgreSQL 13 reached End of Life in November 2025 and will no longer receive security patches. Upgrading to PostgreSQL 16 is recommended, but Faddom will continue to work on PostgreSQL 13 if you choose not to upgrade.
If you choose to upgrade, note that the process is manual and runs after the main upgrade completes. Faddom will not be accessible during this time.
Linux
Connect to the server via SSH
If you have a separate database server (split-installation) you will need to
Copy the script to the database server
scp /cd /opt/FaddomServerUpgrade/scripts/upgrade_to_postgresql16.shscript.sh faddom@<DBIP>:/tmp
Run the script
On a single-instance server of Faddom
sudo ./opt/FaddomServerUpgrade/scripts/upgrade_to_postgresql16.shOn a split installation
SSH to the database server
cd /tmpsudo ./upgrade_to_postgresql16.sh
Windows
Connect to the Faddom server via RDP
Open File Manager and navigate to
C:\Program Files\Faddom\SetupLocate the file
upgradeToPostgresql16.batRight-click the file and select Run as Administrator
How To Upgrade a Remote Proxy
The Faddom proxy will automatically upgrade and will remain on Tomcat 9 and Java 11. If you wish to upgrade Tomcat and Java on the proxy, you will need to redeploy the proxy.
Windows
Connect to the Faddom server via RDP
Open
Control Panel > Add or Remove ProgramsUninstall the
Faddom ProxyOpen Windows services and confirm the
Faddom Apache ProxyThe service is deleted. If not, do the followingOpen CMD as Administrator
Run the command
sc delete FaddomProxy
Install the proxy according to the guide How to Set Up the Faddom Proxy
Linux
Delete the Faddom Proxy VM
Redeploy the VM using the same IP to ensure the firewall rules do not need further changes
