Skip to content

[Bug] [Multi-node Management] Node becomes inaccessible after changing SSH authentication method from web panel #12608

@Yourdaylight

Description

@Yourdaylight

Contact Information

No response

1Panel Version

v2.1.8

Problem Description

I encountered an issue with the multi-node management feature in 1Panel. After changing the SSH authentication method of a child node from the web panel, the node becomes inaccessible and cannot be managed properly.

Steps to Reproduce

Steps to Reproduce:

  • On the main node (Node A), add two child nodes (Node B and Node C) using SSH authentication
    0 Switch the panel from the main node (A) to child node B
  • On node B, modify the SSH management method to key-based authentication
  • Switch back to the main node (A)
  • Check the node management page

The expected correct result

Expected Behavior:

Node B should remain accessible and manageable from the main node
The SSH configuration change should be properly synchronized or handled

Actual Behavior:

  • Node management reports an error for Node B (showing as abnormal)
  • The node management page still displays the old SSH authentication method
  • Unable to switch the panel to Node B anymore
  • Node B becomes completely inaccessible from the multi-node management

Related log output

Additional Information

No response

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions