1/4
How to access worker node SSH?

smnoufal Lv1  Posted 2026-Sep-27 16:40

how to access worker node ssh

admin has solved this question and earned 10 coins.

Posting a reply earns you 2 coins. An accepted reply earns you 20 coins and another 10 coins for replying within 10 minutes. (Expired) What is Coin?

Enter your mobile phone number and company name for better service. Go


To SSH into a worker node in SKE, you need to first enable the SSH Port and configure the SKE O&M Password in the SCP management platform. After that, you can use an SSH client to connect to the worker node's IP address on the enabled SSH port【21†L1-L3】.

Before You Start

- Required: You must have access to the SCP management platform with sufficient privileges to configure Remote Maintenance settings for the Kubernetes Engine service.

Configuration Steps

1. Log in to SCP, go to Compute > Kubernetes Engine > Settings > Remote Maintenance, and click Enable next to SSH Port【21†L6-L10】.

2. On the same page, click Configure next to SKE O&M Password【21†L12-L16】.

3. Enter your SCP login user password for authentication when prompted【21†L18-L20】.

4. Configure the O&M password that will be used for SSH access to the SKE VM【21†L22-L25】.

5. Use an SSH client to connect to the worker node using:
   - Host: the worker node's IP address
   - Port: the SSH port enabled in step 1
   - Username: appropriate user for the SKE VM
   - Password: the O&M password set in step 4

Notes


- These steps apply to SKE 2.2.0 and later. For earlier SKE versions, refer to the corresponding user manual for the specific remote maintenance configuration procedure.
- The SSH port and O&M password settings affect all SKE VMs managed by that SCP instance, including worker nodes.
- Ensure network connectivity exists between your SSH client and the worker node on the enabled SSH port.
Is this answer helpful?
Newbie199792 Lv1  Posted 2026-Sep-30 15:12
  
The article features a simple yet engaging presentation. The information selected is highly relevant to the topic and easy to remember. I believe this is a worthwhile read for anyone looking to learn more or gain knowledge in this area.
Korchai Lv2  Posted 2026-Sep-30 01:03
  
Hi,

Locate the IP address of the *worker node*.
Make sure the IP address can be reached by your computer.
Launch an SSH client, like Windows Terminal or PuTTY.
When prompted, provide the SSH password.
Prosi Lv4  Posted 2026-Sep-28 21:31
  
Hi,

Find the *worker node* IP address.
Ensure your PC can reach that IP address.
Open an SSH client such as PuTTY or Windows Terminal.
Enter the SSH password when prompted.
Muhammad Abid Lv3  Posted 2026-Sep-28 12:21
  
If you mean a Sangfor SCP worker node, SSH access is normally done using the worker node’s management IP.

From Windows

Open PowerShell / CMD:

ssh root@<Worker-Node-IP>

Example:

ssh root@192.168.10.21

Then enter the SSH password when prompted.

If SSH is on a non-standard port

ssh -p <port> root@<Worker-Node-IP>

If you don't know the Worker Node IP

In SCP, check the cluster/host/node management information and identify the worker node's management IP.

If you tell me your SCP version (e.g. 6.11.3) and whether you are trying to SSH from Windows or another SCP node, I can give you the exact procedure.
Newbie380273 Lv2  Posted 2026-Sep-28 00:34
  

Hello,

For Sangfor Kubernetes Engine (SKE), you cannot directly SSH to worker node with public IP. You need to access via the management / bastion.

Please try this:

1.  Via SKE Console:
    Go to SKE -> Clusters -> Your Cluster -> Nodes -> Click on Worker Node -> Remote Terminal / SSH. Use the SSH key that you configured during cluster creation.

2.  Via kubectl:
    If you have kubectl access to the master:
    kubectl get nodes -o wide (to get worker internal IP)
    Then from master node / bastion host:
    ssh -i your-key.pem root@<worker-internal-ip>

3.  Check Security Group / Firewall:
    Make sure port 22 is allowed from your bastion / master to worker nodes in SKE security policy.

If you deployed SKE on HCI / aCloud, you can also access worker VM console directly from HCI console -> VM -> VNC.

Default user is usually "root" or "sangfor" depending on your image. Use the SSH key pair you uploaded during SKE deployment.

Thank you.
Newbie900829 Lv2  Posted 2026-Sep-27 17:48
  
Hi,

To block Proton VPN, blocking only "Proxy Tool" is not enough.

Please apply these steps on your NGAF-1100A:

1. Go to System > Upgrade and update the Application Signature to latest.
2. In Application Control, create a LAN to WAN Deny policy and add these Categories: Proxy Tool, VPN, Anonymizer, and Tunnel.
3. Enable SSL Content Inspection for LAN to WAN. Without this, Proton VPN cannot be detected.
4. Also block DoH, DoT, and UDP 443 (QUIC) in Application Control to prevent DNS bypass.
5. Move this policy to the top and clear all sessions from Diagnostics > Session Monitor.

After this, please test again.

Hope this helps!
Newbie006434 Lv2  Posted 2026-Sep-27 17:37
  
You can access SKE worker node via SSH from the master node. SSH to your master node first, then run kubectl get nodes -o wide to get worker IP, then ssh root@<worker-ip>. You can also access it via HCI console > VM > Open Console if SSH is disabled.

I Can Help:

Change

Board Leaders