[GH-ISSUE #40] [Bug]: Update #130

New issue

Closed

opened 2026-03-13 17:14:24 +03:00 by kerem · 2 comments

kerem commented

2026-03-13 17:14:24 +03:00

Owner

Originally created by @tep1997 on GitHub (Feb 23, 2026).
Original GitHub issue: https://github.com/adminsyspro/proxcenter-ui/issues/40

Bug Description

I'm following the instructions below for updating a Docker instance, but I still end up with vers. 1.2.0.

Steps to Reproduce

cd to /docker/proxcenter ( there is no /opt/proxcenter directory)
docker compose down
docker compose pull && docker compose up -d
docker compose restart

Expected Behavior

New version installed.

Actual Behavior

Same version remains.

ProxCenter Version

1.2.0

Proxmox VE Version

No response

Browser

No response

Logs / Screenshots

No response

Originally created by @tep1997 on GitHub (Feb 23, 2026). Original GitHub issue: https://github.com/adminsyspro/proxcenter-ui/issues/40 ### Bug Description I'm following the instructions below for updating a Docker instance, but I still end up with vers. 1.2.0. <img width="876" height="369" alt="Image" src="https://github.com/user-attachments/assets/41f2cf29-d233-41a4-9362-6a933d0543b2" /> ### Steps to Reproduce cd to /docker/proxcenter ( there is no /opt/proxcenter directory) docker compose down docker compose pull && docker compose up -d docker compose restart ### Expected Behavior New version installed. ### Actual Behavior Same version remains. ### ProxCenter Version 1.2.0 ### Proxmox VE Version _No response_ ### Browser _No response_ ### Logs / Screenshots _No response_

kerem

2026-03-13 17:14:24 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-13 17:14:40 +03:00

Author

Owner

@adminsyspro commented on GitHub (Feb 23, 2026):

Hi @tep1997,

Thanks for reporting this! You're right — the displayed version doesn't change after updating. This is actually a bug on our side: we forgot to bump the version string in the source code when we released v1.3.0. So even if you successfully pulled the latest image, the UI still shows "1.2.0".

Your docker compose pull likely worked correctly — you probably already have the v1.3.0 code running. You can verify by checking the commit SHA in the About dialog (it should match the latest commit).

We're pushing a fix now to update the displayed version to 1.3.0. After we rebuild the image, a simple docker compose pull && docker compose up -d will show the correct version.

Sorry for the confusion!

@adminsyspro commented on GitHub (Feb 23, 2026): Hi @tep1997, Thanks for reporting this! You're right — the displayed version doesn't change after updating. This is actually a bug on our side: we forgot to bump the version string in the source code when we released v1.3.0. So even if you successfully pulled the latest image, the UI still shows "1.2.0". **Your `docker compose pull` likely worked correctly** — you probably already have the v1.3.0 code running. You can verify by checking the commit SHA in the About dialog (it should match the [latest commit](https://github.com/adminsyspro/proxcenter-ui/commits/main)). We're pushing a fix now to update the displayed version to 1.3.0. After we rebuild the image, a simple `docker compose pull && docker compose up -d` will show the correct version. Sorry for the confusion!

kerem commented

2026-03-13 17:14:45 +03:00

Author

Owner

@tep1997 commented on GitHub (Feb 23, 2026):

Yes, the commit matches. Thanks for the update!

@tep1997 commented on GitHub (Feb 23, 2026): Yes, the commit matches. Thanks for the update!