Hello Support team,
My company is using 2.2.x and I would like to upgrade to the next stable release 2.3 instead of the active 2.4 which may come with new features and bugs.
Could you please guide me to where I can find the method for the upgrade to 2.3?
Thank you.
SW
[Solved] Is there a path to upgrade from 2.2 to 2.3 instead of 2.4?
Hi,
for sure. Can you please specify for which operating system the new version needs to be installed? Then I can send you the exact link.
You can also do it yourself in the following way. Please, download the latest version for the operating system of your choice from: https://unimus.net/download.html. After that you need to copy a link address and edit it to version 2.3.3 (or any other)
E.g.
Latest version for Platform independent (Linux / Unix / Mac):
https://download.unimus.net/unimus/-%20Latest/Unimus.jar
Version 2.3.3 for Platform independent (Linux / Unix / Mac):
https://download.unimus.net/unimus/2.3.3/Unimus.jar
for sure. Can you please specify for which operating system the new version needs to be installed? Then I can send you the exact link.
You can also do it yourself in the following way. Please, download the latest version for the operating system of your choice from: https://unimus.net/download.html. After that you need to copy a link address and edit it to version 2.3.3 (or any other)
E.g.
Latest version for Platform independent (Linux / Unix / Mac):
https://download.unimus.net/unimus/-%20Latest/Unimus.jar
Version 2.3.3 for Platform independent (Linux / Unix / Mac):
https://download.unimus.net/unimus/2.3.3/Unimus.jar
JAz,
We do not have a separate Debian installer. We have a General Linux installer, but it has no option to install a specific version.
https://download.unimus.net/unimus/<whichever Unimus Version you want>/Unimus.jar
You can get the .jar for Unimus for a specific version by replacing the numbers above.
I went back to 1.1.0 and it downloads.
You should be good to drop the new .jar file at:
/opt/unimus/Unimus.jar
Installing Java is the only issue. If you use our installer, it installs it. If not, you will need Java 8 for old Unimus versions. How to install Java depends on your particular OS / distro (as mentioned above, JRE is sufficient, Unimus does not need the JDK).
As mentioned please ensure you install Java 8 for Unimus 1.x, or 11 for Unimus version 2.5.0 or older. Java 17 is also supported starting from version 2.5.1.
Side note, if you are okay with running Docker, you can get most of the more recent Unimus Versions directly downloaded and running with little effort with Docker. I would highly recommend looking at that as an option if you seriously want to run older versions of Unimus.
We do not have a separate Debian installer. We have a General Linux installer, but it has no option to install a specific version.
https://download.unimus.net/unimus/<whichever Unimus Version you want>/Unimus.jar
You can get the .jar for Unimus for a specific version by replacing the numbers above.
I went back to 1.1.0 and it downloads.
You should be good to drop the new .jar file at:
/opt/unimus/Unimus.jar
Installing Java is the only issue. If you use our installer, it installs it. If not, you will need Java 8 for old Unimus versions. How to install Java depends on your particular OS / distro (as mentioned above, JRE is sufficient, Unimus does not need the JDK).
As mentioned please ensure you install Java 8 for Unimus 1.x, or 11 for Unimus version 2.5.0 or older. Java 17 is also supported starting from version 2.5.1.
Side note, if you are okay with running Docker, you can get most of the more recent Unimus Versions directly downloaded and running with little effort with Docker. I would highly recommend looking at that as an option if you seriously want to run older versions of Unimus.
Thanks. The lack of being able to select a version made this upgrade VERY difficult. BC "reasons" we were forced to restore from a VERY old backup - v1.10.4 to be exact. But there was no path forward. Installing latest (2.8.x) continuously failed - unable to update the DB errors.Tommy.c wrote: ↑Mon Apr 06, 2026 9:13 pmJAz,
We do not have a separate Debian installer. We have a General Linux installer, but it has no option to install a specific version.
https://download.unimus.net/unimus/<whichever Unimus Version you want>/Unimus.jar
You can get the .jar for Unimus for a specific version by replacing the numbers above.
I went back to 1.1.0 and it downloads.
You should be good to drop the new .jar file at:
/opt/unimus/Unimus.jar
Installing Java is the only issue. If you use our installer, it installs it. If not, you will need Java 8 for old Unimus versions. How to install Java depends on your particular OS / distro (as mentioned above, JRE is sufficient, Unimus does not need the JDK).
As mentioned please ensure you install Java 8 for Unimus 1.x, or 11 for Unimus version 2.5.0 or older. Java 17 is also supported starting from version 2.5.1.
Side note, if you are okay with running Docker, you can get most of the more recent Unimus Versions directly downloaded and running with little effort with Docker. I would highly recommend looking at that as an option if you seriously want to run older versions of Unimus.
I know it's an edge case but this might be something you all should consider.
In my instance I did end up figuring out that I could get docker version in 1.10.4 and since this is a small install w/ HSQL, it wasn't too difficult to migrate.
From there I had to move SPECIFICALLY to 2.0 (not 2.1, not 2.0.1 - 2.0.0)
Once that succeeded I still couldn't get straight to 2.8. What worked for me was 2.0 -> 2.2.smth -> 2.4.(3 I think) -> 2.6.2 then 2.8.0.
Obv taking backups at each step, having to restore when I "jumped forward" too far, etc.
Anyway, done now. Maybe this will help someone in the future.
J.
I will talk to the Devs and we will work on documenting the order of operations for upgrading. That is something we should have better documentation about. Thank you for your notes.
Side note, I did talk with Tomas and he wanted me to clarify that once you have a working Unimus instance, you can just keep dropping the new Unimus.jar file into the installation directory and restarting the application and you will be good to go. That doesn't help much for your situation where you were needing to go through so many different versions and have the DB updated as well. But the application itself is pretty intelligent and the latest versions will run on any of the previously supported Java versions.
Side note, I did talk with Tomas and he wanted me to clarify that once you have a working Unimus instance, you can just keep dropping the new Unimus.jar file into the installation directory and restarting the application and you will be good to go. That doesn't help much for your situation where you were needing to go through so many different versions and have the DB updated as well. But the application itself is pretty intelligent and the latest versions will run on any of the previously supported Java versions.
Sorry for another question in the same thread.
I'm still running 2.2.4 for the sake of one-man bank doing most of the work in the region.
My current and the only instance is running in another country.
Is it possible I run another instance (2.8) as of another zone for the device migration before I upgrade the original instance to 2.8?
I just can't take the risk to ruin the whole database though I was thinking to use oxidized (just for the backup purpose).
Steven
remark: the key person who helped setup the docker for the current unimus instance left a while ago and hardly for me to understand how it was done.
I'm still running 2.2.4 for the sake of one-man bank doing most of the work in the region.
My current and the only instance is running in another country.
Is it possible I run another instance (2.8) as of another zone for the device migration before I upgrade the original instance to 2.8?
I just can't take the risk to ruin the whole database though I was thinking to use oxidized (just for the backup purpose).
Steven
remark: the key person who helped setup the docker for the current unimus instance left a while ago and hardly for me to understand how it was done.
Hi, you can definitely run another instance on 2.8, you can even use the same license key for it as the "main" instance. It will pull the device list from the main instance, so it should be fast to setup.
You should be able to update to 2.8 directly quite easily. It's likely the person used a "docker-compose.yml" file. In there, you can just set the image tag to 2.8.0. If it's using "latest" right now, you can just do "docker compose pull; docker compose stop; docker compose up -d".
Unimus does DB upgrades in sequence, and an update is only started if a previous one succeeded. In essence, the db will never "break", it's just possible an update fails - but that will in no way damage data, since updates are atomic (either it succeeds as a whole, or nothing in the DB is changed).
Hi Tomas,Tomas wrote: ↑Fri May 01, 2026 3:45 amHi, you can definitely run another instance on 2.8, you can even use the same license key for it as the "main" instance. It will pull the device list from the main instance, so it should be fast to setup.
You should be able to update to 2.8 directly quite easily. It's likely the person used a "docker-compose.yml" file. In there, you can just set the image tag to 2.8.0. If it's using "latest" right now, you can just do "docker compose pull; docker compose stop; docker compose up -d".
Unimus does DB upgrades in sequence, and an update is only started if a previous one succeeded. In essence, the db will never "break", it's just possible an update fails - but that will in no way damage data, since updates are atomic (either it succeeds as a whole, or nothing in the DB is changed).
I appreciated for your reply so much.
I'll setup a test instance and see if it works. I just can't take any risks to corrupt the working setup
