[GH-ISSUE #30] [Bug]: SSH Fetch error when putting host in mainteance mode. #124

New issue

Closed

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

kerem commented

2026-03-13 17:13:37 +03:00

Owner

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

Bug Description

Hello,
We are trying to understand what is causing this. All 3 hosts on the cluster do the same thing. SSH is enabled and can be accessed manually through ssh to confirm user/password.

Steps to Reproduce

Inventory
Right click Host
Enter Maintenance Mode
Click Confirm
Fetch Error as seen above.

Expected Behavior

Host going into maintenance mode

Actual Behavior

fetch error

ProxCenter Version

latest

Proxmox VE Version

latest

Browser

Firefox

Logs / Screenshots

Originally created by @Trembler34 on GitHub (Feb 19, 2026). Original GitHub issue: https://github.com/adminsyspro/proxcenter-ui/issues/30 ### Bug Description Hello, We are trying to understand what is causing this. All 3 hosts on the cluster do the same thing. SSH is enabled and can be accessed manually through ssh to confirm user/password. ### Steps to Reproduce 1. Inventory 2. Right click Host 3. Enter Maintenance Mode 4. Click Confirm 5. Fetch Error as seen above. ### Expected Behavior Host going into maintenance mode ### Actual Behavior fetch error ### ProxCenter Version latest ### Proxmox VE Version latest ### Browser Firefox ### Logs / Screenshots <img width="440" height="269" alt="Image" src="https://github.com/user-attachments/assets/92589795-e3cb-4edd-84f5-74e3e30aaaa1" /> <img width="396" height="177" alt="Image" src="https://github.com/user-attachments/assets/a1239e39-5166-4779-a16f-c0794f446b95" />

kerem

2026-03-13 17:13:37 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-13 17:13:52 +03:00

Author

Owner

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

Hi! Thanks for reporting this.

The "Fetch Error" you're seeing happens because maintenance mode (and VM unlock) rely on SSH commands that were being routed through the Go orchestrator (ORCHESTRATOR_URL/api/v1/ssh/exec). In Community edition, the orchestrator isn't running, so the request fails with a network error — which surfaces as a generic "Fetch Error" in the UI.

This is now fixed in commit 044ed8f. The SSH layer now falls back to a direct SSH connection (using the ssh2 library in Node.js) when the orchestrator is unavailable. So maintenance mode, VM unlock, and SSH connection testing should all work without the orchestrator.

To get the fix, pull the latest version and rebuild. Let us know if the issue persists after updating!

@adminsyspro commented on GitHub (Feb 20, 2026): Hi! Thanks for reporting this. The "Fetch Error" you're seeing happens because maintenance mode (and VM unlock) rely on SSH commands that were being routed through the Go orchestrator (`ORCHESTRATOR_URL/api/v1/ssh/exec`). In Community edition, the orchestrator isn't running, so the request fails with a network error — which surfaces as a generic "Fetch Error" in the UI. **This is now fixed** in commit 044ed8f. The SSH layer now falls back to a direct SSH connection (using the `ssh2` library in Node.js) when the orchestrator is unavailable. So maintenance mode, VM unlock, and SSH connection testing should all work without the orchestrator. To get the fix, pull the latest version and rebuild. Let us know if the issue persists after updating!

kerem commented

2026-03-13 17:13:57 +03:00

Author

Owner

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

Hi, unfortunately it's still happening. I updated, rebooted for good measure, fresh login, attempted maintenance mode and it still throws the fetch error.

Just to confirm this is correct, this is what i see..

And to update i did

cd /opt/proxcenter && docker compose pull

it definitely appeared to pull the new image.

Is that correct process?

@Trembler34 commented on GitHub (Feb 20, 2026): Hi, unfortunately it's still happening. I updated, rebooted for good measure, fresh login, attempted maintenance mode and it still throws the fetch error. Just to confirm this is correct, this is what i see.. <img width="286" height="142" alt="Image" src="https://github.com/user-attachments/assets/184d57bd-fe59-4189-8181-679843413ee7" /> And to update i did cd /opt/proxcenter && docker compose pull it definitely appeared to pull the new image. Is that correct process?