[GH-ISSUE #75] [Feature]: Ability to choose subnet for SSH when using Rolling Update #92

New issue

Closed

opened 2026-03-07 19:27:32 +03:00 by kerem · 1 comment

kerem commented

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

Owner

Originally created by @nothing-fr on GitHub (Mar 6, 2026).
Original GitHub issue: https://github.com/adminsyspro/proxcenter-ui/issues/75

Feature Description

I would like to be able to choose which network to use to connect to my Proxmox servers via SSH, as I have several interfaces/networks configured.

The connection test when adding the PVE cluster in Proxcenter works fine, and SSH connects via the correct interfaces. However, when the rolling update is launched, it tries to connect via SSH using the wrong network and therefore fails...

Problem / Use Case

Rolling updates fail because of SSH access via the wrong network.

Proposed Solution

Ability to choose the SSH access address in ProxCenter...

Alternatives Considered

create a separate script or do it manually...

How important is this feature to you?

Critical for my workflow

Additional Context

No response

Contribution

I would be willing to help implement this feature

Originally created by @nothing-fr on GitHub (Mar 6, 2026). Original GitHub issue: https://github.com/adminsyspro/proxcenter-ui/issues/75 ### Feature Description I would like to be able to choose which network to use to connect to my Proxmox servers via SSH, as I have several interfaces/networks configured. The connection test when adding the PVE cluster in Proxcenter works fine, and SSH connects via the correct interfaces. However, when the rolling update is launched, it tries to connect via SSH using the wrong network and therefore fails... ### Problem / Use Case - Rolling updates fail because of SSH access via the wrong network. ### Proposed Solution - Ability to choose the SSH access address in ProxCenter... ### Alternatives Considered - create a separate script or do it manually... ### Category Infrastructure Management ### How important is this feature to you? Critical for my workflow ### Additional Context _No response_ ### Contribution - [ ] I would be willing to help implement this feature

kerem

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

closed this issue
added the
enhancement

feature-request
labels

kerem commented

2026-03-13 17:16:26 +03:00

Author

Owner

@adminsyspro commented on GitHub (Mar 6, 2026):

Hi @nothing-fr,

This has been implemented and is now live! 🎉

When launching a Rolling Update, you'll now see an SSH Addresses section in the configuration step of the wizard. For each node, you can:

Auto-detect (default) — ProxCenter uses the management IP as before
Select a specific interface — all network interfaces with their IPs are listed per node (fetched directly from Proxmox)
The selected address is saved per node, so you only need to configure it once

This should solve your issue with rolling updates trying to connect via the wrong network.

Let us know if everything works as expected on your setup!

@adminsyspro commented on GitHub (Mar 6, 2026): Hi @nothing-fr, This has been implemented and is now live! 🎉 When launching a Rolling Update, you'll now see an **SSH Addresses** section in the configuration step of the wizard. For each node, you can: - **Auto-detect (default)** — ProxCenter uses the management IP as before - **Select a specific interface** — all network interfaces with their IPs are listed per node (fetched directly from Proxmox) - The selected address is **saved per node**, so you only need to configure it once This should solve your issue with rolling updates trying to connect via the wrong network. Let us know if everything works as expected on your setup!

kerem referenced this issue

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

[PR #92] build(deps): bump actions/checkout from 4 to 6 #178