diff --git a/content/rancher/v2.6/en/troubleshooting/kubernetes-components/controlplane/_index.md b/content/rancher/v2.6/en/troubleshooting/kubernetes-components/controlplane/_index.md
index 201c6e30aaf..e27339cb8b5 100644
--- a/content/rancher/v2.6/en/troubleshooting/kubernetes-components/controlplane/_index.md
+++ b/content/rancher/v2.6/en/troubleshooting/kubernetes-components/controlplane/_index.md
@@ -37,4 +37,12 @@ The logging of the containers can contain information on what the problem could
 docker logs kube-apiserver
 docker logs kube-controller-manager
 docker logs kube-scheduler
+```
+
+# RKE2 Server Logging
+
+If Rancher provisions an RKE2 cluster that can't communicate with Rancher, you can run this command on a server node in the downstream cluster to get the RKE2 server logs:
+
+```
+journalctl -u rke2-server -f
 ```
\ No newline at end of file