Docs on How to Troubleshoot Radius apps

docs/content/community/contributing/github.md

@@ -18,4 +18,14 @@ The source code for Radius is available on GitHub within the [radius repo](https
 
 Documentation is housed at https://github.com/radius-project/docs.
 
-Samples are location at https://github.com/radius-project/samples.
+Samples are located at https://github.com/radius-project/samples.
+
+## Troubleshooting common issues
+
+### Visual Studio not authorized for single sign-on
+
+If you receive an error saying Visual Studio Code or another application is not authorized to clone any of the Radius repositories you may need to re-authorize the GitHub app:
+
+1. Open a browser to https://github.com/settings/applications
+1. Find the applicable app and select Revoke
+1. Reopen app on local machine and re-auth

docs/content/guides/author-apps/aws/howto-aws-resources/index.md

@@ -120,7 +120,7 @@ If you have issues with the sample application, where the container doesn't conn
     ```bash
     rad resource logs containers frontend -a s3app
     ```
-Also please make sure to [open an Issue](https://github.com/radius-project/radius/issues/new?assignees=&labels=kind%2Fbug&template=bug.md&title=%3CBUG+TITLE%3E) if you encounter a generic `Internal server error` message or an error message that is not self-serviceable, so we can address the root error not being forwarded to the user.
+Also make sure to [open an Issue](https://github.com/radius-project/radius/issues/new/choose) if you encounter a generic `Internal server error` message or an error message that is not self-serviceable, so we can address the root error not being forwarded to the user.
 
 ## Further Reading
 

docs/content/guides/deploy-apps/howto-delete/index.md

@@ -10,7 +10,7 @@ tags: ["delete"]
 
 ## Pre-requisites
 
-A [deployed application]({{< ref deploy-apps >}}) in a Radius environment.
+- A [deployed application]({{< ref deploy-apps >}}) in a Radius environment.
 
 ## Step 1: Delete the Radius application from the environment 
 

docs/content/guides/deploy-apps/howto-troubleshootapps/index.md

@@ -0,0 +1,43 @@
+---
+type: docs
+title: "How-To: Troubleshoot applications"
+linkTitle: "Troubleshoot apps"
+description: "Learn how to troubleshoot issues with the Radius application"
+weight: 900
+categories: "How-To"
+tags: ["troubleshooting"]
+---
+
+## Pre-requisites
+
+- A [deployed application]({{< ref deploy-apps >}}) in a Radius environment.
+
+## Step 1: Port-forward container to your local machine
+
+Use the below command to port-forward the container to your local machine. This enables you to access the container from your local machine.
+
+```bash
+rad resource expose containers <container_name> -a <app_name> --port <port_number>
+```
+Refer to [`rad resource expose`]({{< ref rad_resource_expose >}}) for more details on the command.
+
+## Step 2: Inspect container logs
+
+If your Radius application is unresponsive or does not connect to its dependencies, Use the below command to inspect logs from container:
+
+```bash
+rad resource logs containers frontend -a <app_name>
+```
+
+> Also refer to the [connections section]({{< ref "guides/author-apps/containers/overview#connections" >}}) to know about the naming convention of the environment variables and inspect if your application uses the right variables. 
+
+## Step 4: Inspect control-plane logs
+
+If you hit errors while deploying the application, look at the control plane logs to see if there are any errors. You can use the following command to view the logs:
+
+```bash
+rad debug-logs
+```
+Inspect the UCP and DE logs to see if there are any errors  
+
+>Also make sure to [open an Issue](https://github.com/radius-project/radius/issues/new/choose) if you encounter a generic `Internal server error` message or an error message that is not self-serviceable, so we can address the root error not being forwarded to the user.