starred/proxcenter-ui

Fork 0

mirror of https://github.com/adminsyspro/proxcenter-ui.git synced 2026-04-25 14:35:56 +03:00

[GH-ISSUE #49] [Bug]: Upgrade Node - Fetch Failed #62

New issue

Closed

opened 2026-03-07 19:27:06 +03:00 by kerem · 4 comments

kerem commented

2026-03-07 19:27:06 +03:00

Owner

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

Bug Description

Trying to update the node, click on start upgrade and get the fetch failed error.

Steps to Reproduce

Click the update notification > upgrade > Start Update

Expected Behavior

Node upgrades

Actual Behavior

Fetch Error

ProxCenter Version

latest

Proxmox VE Version

latest

Browser

Chrome

Logs / Screenshots

Originally created by @Trembler34 on GitHub (Feb 25, 2026). Original GitHub issue: https://github.com/adminsyspro/proxcenter-ui/issues/49 ### Bug Description Trying to update the node, click on start upgrade and get the fetch failed error. ### Steps to Reproduce Click the update notification > upgrade > Start Update ### Expected Behavior Node upgrades ### Actual Behavior Fetch Error ### ProxCenter Version latest ### Proxmox VE Version latest ### Browser Chrome ### Logs / Screenshots <img width="609" height="582" alt="Image" src="https://github.com/user-attachments/assets/15f2c735-42a6-484c-b50b-d1f7c21dd12f" />

kerem

2026-03-07 19:27:06 +03:00

closed this issue
added the
bug
label

kerem commented

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

Author

Owner

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

Fixed in commit 06f3742.

Root cause: NodeUpdateDialog called the Go orchestrator (/api/v1/orchestrator/rolling-updates), which is not deployed in Community Edition → fetch() fails with ECONNREFUSED.

Fix: Single-node updates now use direct SSH instead of the orchestrator:

New API routes: POST/GET /api/v1/connections/:id/nodes/:node/upgrade + POST .../upgrade/reboot
NodeUpdateDialog rewritten to use the SSH-based flow (start, poll logs, auto-reboot)
Updates tab is now always accessible for standalone nodes (no longer Enterprise-gated)
Warning displayed if SSH is not configured on the connection
Cluster rolling updates remain Enterprise-only via the orchestrator (unchanged)

@adminsyspro commented on GitHub (Feb 25, 2026): Fixed in commit 06f3742. **Root cause**: `NodeUpdateDialog` called the Go orchestrator (`/api/v1/orchestrator/rolling-updates`), which is not deployed in Community Edition → `fetch()` fails with `ECONNREFUSED`. **Fix**: Single-node updates now use **direct SSH** instead of the orchestrator: - New API routes: `POST/GET /api/v1/connections/:id/nodes/:node/upgrade` + `POST .../upgrade/reboot` - `NodeUpdateDialog` rewritten to use the SSH-based flow (start, poll logs, auto-reboot) - Updates tab is now always accessible for standalone nodes (no longer Enterprise-gated) - Warning displayed if SSH is not configured on the connection - Cluster rolling updates remain Enterprise-only via the orchestrator (unchanged)

kerem commented

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

Author

Owner

@Trembler34 commented on GitHub (Feb 25, 2026):

It saying SSH is not enabled but you can see it is and it works.

@Trembler34 commented on GitHub (Feb 25, 2026): It saying SSH is not enabled but you can see it is and it works. <img width="149" height="139" alt="Image" src="https://github.com/user-attachments/assets/5f75f73c-2e64-4b26-a1dd-08d4c2fa36f2" /> <img width="584" height="528" alt="Image" src="https://github.com/user-attachments/assets/77a9d1b7-6fd5-49c2-b7d8-a2a07efdc0f4" />

kerem commented

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

Author

Owner

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

Fix pushed in commit 963c25a.

Root cause: The connection API returns { data: { sshEnabled: ... } } but the dialog was reading json.sshEnabled at the top level — which is always undefined (falsy), so the SSH warning was always triggered regardless of your actual SSH configuration.

Fix: Changed the check to read json.data?.sshEnabled instead.

Please update and confirm the issue is resolved on your end — keeping this open until then.

@adminsyspro commented on GitHub (Feb 26, 2026): Fix pushed in commit 963c25a. **Root cause:** The connection API returns `{ data: { sshEnabled: ... } }` but the dialog was reading `json.sshEnabled` at the top level — which is always `undefined` (falsy), so the SSH warning was always triggered regardless of your actual SSH configuration. **Fix:** Changed the check to read `json.data?.sshEnabled` instead. Please update and confirm the issue is resolved on your end — keeping this open until then.

kerem commented

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

Author

Owner

@Trembler34 commented on GitHub (Feb 26, 2026):

Its working now.. Thank you.

@Trembler34 commented on GitHub (Feb 26, 2026): Its working now.. Thank you.

kerem referenced this issue

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

[PR #62] [CLOSED] build(deps-dev): bump prisma from 7.4.0 to 7.4.2 in /frontend #174