From b3c100442fe5cd2e49597818be37cde33c8e98bf Mon Sep 17 00:00:00 2001 From: Caleb Bron Date: Thu, 27 Jun 2019 09:49:39 -0700 Subject: [PATCH] sublink and port arent always available --- .../workload/quickstart-deploy-workload-nodeport/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.x/en/quick-start-guide/workload/quickstart-deploy-workload-nodeport/_index.md b/content/rancher/v2.x/en/quick-start-guide/workload/quickstart-deploy-workload-nodeport/_index.md index bf150fadc5a..2de08faf907 100644 --- a/content/rancher/v2.x/en/quick-start-guide/workload/quickstart-deploy-workload-nodeport/_index.md +++ b/content/rancher/v2.x/en/quick-start-guide/workload/quickstart-deploy-workload-nodeport/_index.md @@ -60,7 +60,7 @@ From the **Workloads** page, click the link underneath your workload. If your de ### Attention: Cloud-Hosted Sandboxes -When using a cloud-hosted virtual machine, you may not have access to the port running the container. In this event, you can test Nginx in an ssh session on the local machine. Use the port number after the `:` in the link under your workload, which is `31568` in this example. +When using a cloud-hosted virtual machine, you may not have access to the port running the container. In this event, you can test Nginx in an ssh session on the local machine using `Execute Shell`. Use the port number after the `:` in the link under your workload if available, which is `31568` in this example. ```sh gettingstarted@rancher:~$ curl http://localhost:31568