# Latest server edition not working

**URL:** <https://forum.manager.io/t/latest-server-edition-not-working/64821>\
**Category:** Uncategorized\
**Created:** [August 26, 2025, 8:52pm UTC](https://forum.manager.io/t/latest-server-edition-not-working/64821 "2025-08-26T20:52:29Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![skynet104us](https://avatars.discourse-cdn.com/v4/letter/s/c89c15/32.png) [@skynet104us](https://forum.manager.io/u/skynet104us)\
**Post date:** [August 26, 2025, 8:52pm UTC](https://forum.manager.io/t/latest-server-edition-not-working/64821/1 "2025-08-26T20:52:29Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![lubos](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.manager.io/lubos/32/62798_2.png) [@lubos](https://forum.manager.io/u/lubos)\
**Post date:** [August 26, 2025, 11:53pm UTC](https://forum.manager.io/t/latest-server-edition-not-working/64821/2 "2025-08-26T23:53:37Z")

</div>

What does it mean it doesn’t work? Are you getting any error? You need to provide more detail.

---

<div class="post-metadata">

**Author:** ![skynet104us](https://avatars.discourse-cdn.com/v4/letter/s/c89c15/32.png) [@skynet104us](https://forum.manager.io/u/skynet104us)\
**Post date:** [August 27, 2025, 12:40am UTC](https://forum.manager.io/t/latest-server-edition-not-working/64821/3 "2025-08-27T00:40:04Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![lubos](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.manager.io/lubos/32/62798_2.png) [@lubos](https://forum.manager.io/u/lubos)\
**Post date:** [August 27, 2025, 12:45am UTC](https://forum.manager.io/t/latest-server-edition-not-working/64821/4 "2025-08-27T00:45:18Z")

</div>

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:

```bash
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.

---

<div class="post-metadata">

**Author:** ![eko](https://avatars.discourse-cdn.com/v4/letter/e/a8b319/32.png) [@eko](https://forum.manager.io/u/eko)\
**Post date:** [August 27, 2025, 8:32am UTC](https://forum.manager.io/t/latest-server-edition-not-working/64821/5 "2025-08-27T08:32:20Z")

</div>

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:

 ![Managerserverrunning](https://us1.discourse-cdn.com/flex019/uploads/manager1/original/3X/9/b/9b2fad3d59b88d1ab4d55577db2a0f19be4f4b0c.jpeg)

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.

---

<div class="post-metadata">

**Author:** ![lubos](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.manager.io/lubos/32/62798_2.png) [@lubos](https://forum.manager.io/u/lubos)\
**Post date:** [August 27, 2025, 9:00am UTC](https://forum.manager.io/t/latest-server-edition-not-working/64821/6 "2025-08-27T09:00:27Z")

</div>

@eko you are launching it with:

```bash
ManagerServer -port 8080

```

change that to launch it with:

```bash
ManagerServer --urls http://*:8080

```

---

<div class="post-metadata">

**Author:** ![eko](https://avatars.discourse-cdn.com/v4/letter/e/a8b319/32.png) [@eko](https://forum.manager.io/u/eko)\
**Post date:** [August 27, 2025, 9:47am UTC](https://forum.manager.io/t/latest-server-edition-not-working/64821/7 "2025-08-27T09:47:14Z")

</div>

> [@lubos](#):
>
> `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.**

---

<div class="post-metadata">

**Author:** ![eko](https://avatars.discourse-cdn.com/v4/letter/e/a8b319/32.png) [@eko](https://forum.manager.io/u/eko)\
**Post date:** [August 27, 2025, 9:51am UTC](https://forum.manager.io/t/latest-server-edition-not-working/64821/8 "2025-08-27T09:51:45Z")

</div>

i.e.:

 ![Screenshot 2025-08-27 at 10.51.17](https://us1.discourse-cdn.com/flex019/uploads/manager1/original/3X/f/a/fa9d41410b86fefa51686d2be6a7816422d77148.jpeg)

---

<div class="post-metadata">

**Author:** ![lubos](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.manager.io/lubos/32/62798_2.png) [@lubos](https://forum.manager.io/u/lubos)\
**Post date:** [August 27, 2025, 10:03am UTC](https://forum.manager.io/t/latest-server-edition-not-working/64821/9 "2025-08-27T10:03:23Z")

</div>

@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.

---

<div class="post-metadata">

**Author:** ![eko](https://avatars.discourse-cdn.com/v4/letter/e/a8b319/32.png) [@eko](https://forum.manager.io/u/eko)\
**Post date:** [August 27, 2025, 11:39am UTC](https://forum.manager.io/t/latest-server-edition-not-working/64821/10 "2025-08-27T11:39:20Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![success127](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.manager.io/success127/32/13762_2.png) [@success127](https://forum.manager.io/u/success127)\
**Post date:** [August 28, 2025, 6:23pm UTC](https://forum.manager.io/t/latest-server-edition-not-working/64821/11 "2025-08-28T18:23:57Z")

</div>

@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

---

<div class="post-metadata">

**Author:** ![WSJM](https://avatars.discourse-cdn.com/v4/letter/w/a8b319/32.png) [@WSJM](https://forum.manager.io/u/WSJM)\
**Post date:** [August 28, 2025, 6:35pm UTC](https://forum.manager.io/t/latest-server-edition-not-working/64821/12 "2025-08-28T18:35:40Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![midlandgroup](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.manager.io/midlandgroup/32/55974_2.png) [@midlandgroup](https://forum.manager.io/u/midlandgroup)\
**Post date:** [August 28, 2025, 11:00pm UTC](https://forum.manager.io/t/latest-server-edition-not-working/64821/13 "2025-08-28T23:00:16Z")

</div>

If this is happening, i better retain my previous account, not upgrading anytime soon  
I might lose many data

---

<div class="post-metadata">

**Author:** ![lubos](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.manager.io/lubos/32/62798_2.png) [@lubos](https://forum.manager.io/u/lubos)\
**Post date:** [August 29, 2025, 12:45am UTC](https://forum.manager.io/t/latest-server-edition-not-working/64821/14 "2025-08-29T00:45:02Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![anatawiranata](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.manager.io/anatawiranata/32/49532_2.png) [@anatawiranata](https://forum.manager.io/u/anatawiranata)\
**Post date:** [August 29, 2025, 1:05am UTC](https://forum.manager.io/t/latest-server-edition-not-working/64821/15 "2025-08-29T01:05:46Z")

</div>

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:

```auto
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:

```auto
nssm install ManagerServerService

```

 ![image](https://us1.discourse-cdn.com/flex019/uploads/manager1/original/3X/2/c/2c3982a29c811ecbb8993cdea0a4b3d437c18fa2.png)

• 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.

 ![image](https://us1.discourse-cdn.com/flex019/uploads/manager1/original/3X/5/8/58d9f30e4288b8f257b637c41c74479e4534aa01.png)

• 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.

 ![image](https://us1.discourse-cdn.com/flex019/uploads/manager1/original/3X/c/4/c48e560b184f28e52b5d3f3b6acb52304e1662e3.png)

For the `Arguments` field, first see this image below:

 ![image](https://us1.discourse-cdn.com/flex019/uploads/manager1/original/3X/6/6/66c283671284b77d8f706444d714cb834a85168b.png)

• 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:

```auto
--urls http://*:8080 --path "D:\ManagerData"

```

 ![image](https://us1.discourse-cdn.com/flex019/uploads/manager1/original/3X/e/8/e8807ce6a51482642c1915792f5dcd859209f82c.png)

• `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.

 ![image](https://us1.discourse-cdn.com/flex019/uploads/manager1/original/3X/e/1/e13d93671c68ffbc364a9306bdbd63b5c538d8ee.png)

• 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](https://www.manager.io/server-edition), 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.

---

<div class="post-metadata">

**Author:** ![compuit](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.manager.io/compuit/32/66_2.png) [@compuit](https://forum.manager.io/u/compuit)\
**Post date:** [September 30, 2025, 12:30pm UTC](https://forum.manager.io/t/latest-server-edition-not-working/64821/16 "2025-09-30T12:30:46Z")

</div>

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](http://release-assets.githubusercontent.com) ([release-assets.githubusercontent.com](http://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.

---

<div class="post-metadata">

**Author:** ![compuit](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.manager.io/compuit/32/66_2.png) [@compuit](https://forum.manager.io/u/compuit)\
**Post date:** [September 30, 2025, 12:56pm UTC](https://forum.manager.io/t/latest-server-edition-not-working/64821/17 "2025-09-30T12:56:10Z")

</div>

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 ….. 😟

---

<div class="post-metadata">

**Author:** ![eko](https://avatars.discourse-cdn.com/v4/letter/e/a8b319/32.png) [@eko](https://forum.manager.io/u/eko)\
**Post date:** [September 30, 2025, 2:00pm UTC](https://forum.manager.io/t/latest-server-edition-not-working/64821/18 "2025-09-30T14:00:00Z")

</div>

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

```auto
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

```auto
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)

```auto
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)

```auto
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:

```auto
sudo /root/update-manager.sh

```

## THAT’s IT!!

---

<div class="post-metadata">

**Author:** ![compuit](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.manager.io/compuit/32/66_2.png) [@compuit](https://forum.manager.io/u/compuit)\
**Post date:** [September 30, 2025, 2:12pm UTC](https://forum.manager.io/t/latest-server-edition-not-working/64821/19 "2025-09-30T14:12:07Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![compuit](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.manager.io/compuit/32/66_2.png) [@compuit](https://forum.manager.io/u/compuit)\
**Post date:** [September 30, 2025, 5:59pm UTC](https://forum.manager.io/t/latest-server-edition-not-working/64821/20 "2025-09-30T17:59:12Z")

</div>

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

[Next page](https://forum.manager.io/t/latest-server-edition-not-working/64821.md?page=2)
