After upgrading does not work anymore, the last version that works is 25.8.19.2622, i see that less files were uncompressed and does not work
any suggestios.
using ubuntu version.
What does it mean it doesn’t work? Are you getting any error? You need to provide more detail.
I upgraded as usual, however i notice that when decompressing the files, it did not decompress the same amount of the files it usually does, they were like 10 files the most. I had to downgrade until I found one that works and it its the 25.8.19.2066, that one worked just fine. When you install the new version it does to respond when you call it using your browser, even i restart the service or restart the server itself.
Number of files in the package has been decreased. But server edition is confirmed to be working. We are using it to host cloud edition.
What has changed are arguments. When you launch server edition you will now see this:
Syntax:
ManagerServer [options]
Options:
--urls <binding> Kestrel URL(s). Example: http://localhost:5000
Multiple values separated by ';'.
--path <directory> Data directory for Manager.
Examples:
ManagerServer
ManagerServer --urls http://localhost:80
ManagerServer --urls http://*:80 --path "/data/Manager.io"
If you are using non-default port, then use --urls argument. It’s more standard and more flexible.
I have the same problem. After a long time I decided to update Manager from version 25.5.31.2363, today as per usual terminal script that worked for years. Although, Manager Server started in terminal as usual see:
and after a reboot and long wait it just keeps saying in varius browsers (Chrome, Brave, and Safari) and from various computers:
Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.However when using different browsers, Chrome, Brave, and Safari.
I can only conclude that something has changed in the newer Server Edition version since this is the first time this is happening. I have no problem accessing the server using terminal. The server is Ubuntu with the following details:
Operating System: Ubuntu 20.04.6 LTS
Kernel: Linux 5.4.0-216-generic
Architecture: x86-64
Please fix so we can use the application, thanks.
@eko you are launching it with:
ManagerServer -port 8080
change that to launch it with:
ManagerServer --urls http://*:8080
Is getting worse, still same error but now:
manager-server.service: Current command vanished from the unit file, execution of the command list won’t be resumed.
@eko, this is not Manager issue. It’s an error from systemd. Copy and paste that error into ChatGPT which will explain what you need to change and how.
Manager Server is working. Even your console output is indicating Manager Server is running on port 5000.
I fixed it with help from AI, but it is concerning that a script I used for years worked well until I upgraded today from version 25.5.31.2363
I made backups just before running my normal script and if it behaves now differently it is because of changes you made and should have alerted us to.
Thank you for responding.
@lubos Could you please enlighten me how to upgrade to the latest version? Previous I used NSSM to stop and unzip the download over the ManagerServer folder. Then I started the NSSM to run the program. Now with this latest version, I am very confused with the syntax and the path. Should the path be the ManagerServer folder or the AppData/Local/Manager folder? Can I continue to use NSSM? Please provide the step-by-step. Thanks
Can you explain what you did to get it working? I am getting the same errors. However, I don’t use a script. I wget the latest version, extract the tar, and restart the service. When extracting I also saw there were a lot less files.
Thanks in advance!
If this is happening, i better retain my previous account, not upgrading anytime soon
I might lose many data
In the latest version (25.8.29. 2724) I made it so the program still understands the old -port argument. This means your scripts launching ManagerServer can remain unchanged.
I assume you use Windows Server Edition of Manager. Like Lubos said, the number of files in the package has been decreased. But, it doesn’t matter, because we can just execute the ManagerServer.exe file anyway. It’s still the same, and yes we still can use NSSM. But, I use NSSM just for creating Windows Service for Manager. To upgrade (download zip package & unzip), stop & start the service in one click, I created .bat scripts manually. So if I need to upgrade Manager to the newest version or to stop and start (restart) the service, I can just execute those .bat scripts. For now, I’ll try to explain how to install Manager as Windows Service in this new version. Maybe it will helps the windows users.
If you already have Manager as a Windows Service before, remove it first. You can use NSSM for this:
• Use Win+R and type services.msc then click OK.
• Find the Manager service and stop it. For example, the service name I set for Manager is ManagerServerService, so after find this service name, right click and then click stop.
• Open CMD as administrator, then go to directory of nssm.exe file.
• Run this command:
nssm remove ManagerServerService
• Done removing the service.
Now, we can configure a new service for the new version:
• First download the latest zip file of Manager Server Edition for Windows.
• Unzip it and place it on any directory you want.
• Open CMD as administrator again, then run this command:
nssm install ManagerServerService
• In my screenshot, the nssm.exe file is in the D directory. That’s why I enter the D: command first. Yours maybe different.
• Then, It will open the NSSM service installer interface, and ManagerServerService will be automatically set as the Service name below. You can change the Service name as you like.
• In the Path field, click the … button and find the ManagerServer.exe file from the unzipped package before, select the ManagerServer.exe file and open it.
• The Path field and Startup directory field will be filled automatically. All the unzipped file from the zip package of mine is in the D:\ManagerServer directory, so this is the screenshot after selecting the ManagerServer.exe file.
For the Arguments field, first see this image below:
• When we execute the ManagerServer.exe directly this is what we get. In the old version the options is -port and -path, now in the new version we can use –-urls and –-path. By default, if we execute ManagerServer.exe directly, Manager will listen on port 5000, and it will create the Data directory for Manager automatically. From the screenshot, for mine Manager create the Data Directory in the D:\Documents\Manager.io folder automatically. So all the .manager business files, keys, and password for users will be saved here. Now, if we want to change the listening port (for example port 8080), and if we want to use the Data directory that we already have for the old version, we can use this reference to fill the Arguments field in the NSSM service installer before. For example:
--urls http://*:8080 --path "D:\ManagerData"
• D:\ManagerData is my Data directory for Manager from the old version where all of my .manager business file is located. Change it with yours.
• This is an additional or optional setting. You can open the Details tab.
• You can set Display Name and Description here, so in the services.msc instead of ManagerServerService, the service name you’ll see will be the Display name we set here. For example I set it as Manager Server Service. It’s optional and you can change it however you like. For the Startup type keep it automatic. If you don’t configure anything in this tab, it’s fine.
• After finish it, then click the Install service button.
• Now, the service is installed. But, you have to make sure the service is running. Open services.msc again, find the new service we installed, right click and click Start. Now, try open http://localhost:8080 in the browser.
Note:
Make sure to stop the service before you upgrade Manager if there is new update. To upgrade you can just simply download the latest Manager zip package for Windows from this link here, unzip it and replace all of the files and folders in your Manager installation directory.
I hope it can help all Windows users that use Manager Server Edition for Windows.
2 Likes
Just carried out a Manager Server Update from 25.5.8.2317 to latest 25.9.30.2859 which appears to have failed stating
Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems
Testing shows port 443 alive and well.
I do note that the download / install is very small compared to the last update update? Below is the process and all looked normal.
Step 1
Connecting to release-assets.githubusercontent.com (release-assets.githubusercontent.com)|185.199.108.133|:443… connected.
HTTP request sent, awaiting response… 200 OK
Length: 55914758 (53M) [application/octet-stream]
Saving to: ‘/usr/share/manager-server/ManagerServer-linux-x64.tar.gz’
/usr/share/manager-server/Mana 100%[===================================================>] 53.32M 47.9MB/s in 1.1s
2025-10-01 01:04:56 (47.9 MB/s) - ‘/usr/share/manager-server/ManagerServer-linux-x64.tar.gz’ saved [55914758/55914758]
Step 2
root@manager02:~# tar xvzf /usr/share/manager-server/ManagerServer-linux-x64.tar.gz -C /usr/share/manager-server
./
./ManagerComponents.pdb
./ManagerServer
./Tools/
./Tools/win-x64/
./Tools/win-x64/sqlite3.exe
./Assets/
./Assets/Formats.json
./Assets/Users.html
./Assets/Support.html
./Assets/Translations.json
./Assets/Localizations.json
./libe_sqlite3.so
root@manager02:~#
Step 3
Reboot
Has something changed with the update process on Linux? We have updated for years using the 3 steps above with no issue.
In addition thinking it might be the Ubuntu OS I rebooted the server and stepped back to previous OS 22.04.5 releases and the Manager symptom remained the same. So we are confident at this point that it is not the operating system. Guys I am getting frantic ….. 
I had to change with support from @Lubos earlier post and with help of ChatGPT, using Ubuntu server and ended up with the following which made it all work again:
Copy-paste the code block(s) below into Terminal. It will: 1. create /root/update-manager.sh with the right contents, 2. make it executable, and 3. run it once. After that you can update Manager with the final command line each time you want to.
CREATE THE SCRIPT
sudo tee /root/update-manager.sh >/dev/null <<'EOF'
#!/usr/bin/env bash
set -euo pipefail
MS_DIR="/usr/share/manager-server"
MS_BIN="${MS_DIR}/ManagerServer"
MS_URL="https://github.com/Manager-io/Manager/releases/latest/download/ManagerServer-linux-x64.tar.gz"
echo "==> Updating Ubuntu packages..."
if command -v apt-fast >/dev/null 2>&1; then
sudo apt-fast update
sudo apt-fast -y upgrade
else
sudo apt-get update -y
sudo apt-get -y upgrade
fi
sudo apt-get -y autoremove
sudo apt-get -y autoclean
echo "==> Downloading latest ManagerServer..."
tmpdir="$(mktemp -d)"
trap 'rm -rf "$tmpdir"' EXIT
mkdir -p "$MS_DIR"
# ensure curl exists (just in case)
if ! command -v curl >/dev/null 2>&1; then
sudo apt-get update -y
sudo apt-get install -y curl ca-certificates
fi
curl -fL --retry 5 --retry-delay 2 --connect-timeout 10 --max-time 240 \
-o "${tmpdir}/ManagerServer.tgz" "$MS_URL"
echo "==> Installing ManagerServer..."
tar -xzf "${tmpdir}/ManagerServer.tgz" -C "$tmpdir"
sudo install -m 0755 -o root -g root "${tmpdir}/ManagerServer" "$MS_BIN"
echo "==> Restarting manager-server service..."
sudo systemctl daemon-reload
sudo systemctl stop manager-server || true
sudo systemctl reset-failed manager-server || true
sudo systemctl start manager-server
if sudo systemctl is-active --quiet manager-server; then
echo "==> ManagerServer is running ✅"
else
echo "!! ManagerServer failed to start. Showing status:"
sudo systemctl status manager-server --no-pager || true
exit 1
fi
Optional: reload Caddy if installed
if systemctl list-unit-files | grep -q '^caddy.service'; then
echo "==> Reloading Caddy (if running)..."
sudo systemctl reload caddy || sudo systemctl restart caddy || true
fi
Robust version banner (won’t hang)
echo "==> Installed binary version:"
if command -v timeout >/dev/null 2>&1; then
timeout 3 "$MS_BIN" --help 2>&1 | head -n 1 || echo "(skipped: help timed out)"
else
"$MS_BIN" --help 2>&1 | head -n 1 || echo "(skipped: could not read banner)"
fi
Make it executable and run it (0nce)
sudo chmod +x /root/update-manager.sh
sudo /root/update-manager.sh
RUNNING THE SCRIPT:
Next time you want to update Manager on Ubuntu Server just run:
sudo /root/update-manager.sh
THAT’s IT!!
Cheers will try this on a backup of the faulty production server. Will share experience 
OK sadly no joy run the script all looked good checked listening port 443 OK
Processing triggers for man-db (2.12.0-4build2) …
Processing triggers for libc-bin (2.39-0ubuntu8.6) …
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
==> Downloading latest ManagerServer…
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0
100 53.3M 100 53.3M 0 0 35.6M 0 0:00:01 0:00:01 --:–:-- 113M
==> Installing ManagerServer…
==> Restarting manager-server service…
==> ManagerServer is running 
I checked the manager-service status to see if running …. Well it is failing. See below.
sudo systemctl status manager-server
× manager-server.service
Loaded: loaded (/etc/systemd/system/manager-server.service; enabled; preset: enabled)
Active: failed (Result: core-dump) since Wed 2025-10-01 05:18:59 NZDT; 3min 50s ago
Duration: 663ms
Process: 1732 ExecStart=/usr/share/manager-server/ManagerServer -port 8080 -path=/media/network/nas01/Manager/ (code=dumped, signal=ABRT)
Main PID: 1732 (code=dumped, signal=ABRT)
CPU: 306ms
Oct 01 05:18:59 manager02 systemd[1]: manager-server.service: Scheduled restart job, restart counter is at 5.
Oct 01 05:18:59 manager02 systemd[1]: manager-server.service: Start request repeated too quickly.
Oct 01 05:18:59 manager02 systemd[1]: manager-server.service: Failed with result ‘core-dump’.
Oct 01 05:18:59 manager02 systemd[1]: Failed to start manager-server.service.
Upgraded to Ubuntu 24.04.3 LTS same result.
It is interesting to see that the upgrade has picked up an old data path not used since 2021. How the heck did that happen?? The Manager data is on the local host.
How do I get manager to look here /root/.local/share/Manager/ for its data? I am thinking the service will not run because manager does not find its data.
Please point me to Manager Linux Server version 25.5.8.2317 as this update process is a disaster for us.
Just for the record Manager is installed here /usr/share/manager-server on the local host
Data located here /root/.local/share/Manager/ on the local host