How Do I Troubleshoot the VMware Cloud Director service Proxy Client Appliance

You can use the console for the VMware Cloud Director service proxy client appliance to diagnose issues with the appliance VM.

Note: Earlier VMware Cloud Director service proxy client appliance versions don't support the diagnose.sh troubleshooting command. If you attempt to run it and that results in an error, follow the troubleshooting instructions described in How Do I Troubleshoot the Connection of a VMware Cloud Director Instance to an SDDC through VMware Proxy Service.

Procedure

Log in to the OS of the proxy appliance.
Run the command to diagnose any issues with the proxy appliance.
```
diagnose.sh -o OUTPUT_FILE
```
Use the -o to create an output file with the diagnostic results. If you need to contact VMware technical support, providing the output file can help your support representative to assist you faster.

Tip: To edit the proxy appliance OVA properties, navigate to the appliance VM in the vCenter inventory. On the Configure tab, click Settings > vApp Options.

Results

The output file that the command generates contains information that can help you diagnose a number of issues with the reverse proxy client.

Code	Issue
`CDS_RP_100`	You didn't set VMware Cloud services authentication on the client. To fix the issue, set the OVА properties `csp-client-secret` and `csp-client-id` of the appliance VM to be the ID and secret of the OAuth app that is associated with your VMware Cloud services platform organization or regenerate the VMware reverse proxy appliance OVA.
`CDS_RP_101`	You set the authentication information correctly, but the information was invalid. To fix this issue, double check the ID and secret for the OAuth app and, if necessary, regenerate the VMware reverse proxy appliance OVA.
`CDS_RP_102`	You have an invalid network name set on the client. To fix this issue, set the OVA property `vc-name` or regenerate the VMware reverse proxy appliance OVA.
`CDS_RP_103`	You have an invalid organization ID set on the client. To fix this issue, set the OVA property `csp-org-id` with the valid VMware Cloud services platform organization ID and regenerate the reverse proxy appliance OVA. See How Do I Retrieve the ID of My Organization in the Programming with VMware Cloud Director Service API guide.
`CDS_RP_104`	A required outbound target of the proxy client appliance could not be reached. Check the networking logs and ensure that the VM can communicate with this target.
`CDS_RP_105`	You provided correct authentication information, but the authentication information was not valid for your VMware Cloud services platform organization. Double check the OAuth app, whether you're using the correct organization ID, and whether the OAuth app has `provider:network` permissions. To fix this issue, regenerate the VMware reverse proxy appliance OVA.
`CDS_RP_106`	An allowed target that you configured within your network is not reachable from the proxy VM. Ensure that the VM can communicate with this target.
`CDS_RP_107`	Your client can't automatically verify that the update agent is started and active. To fix this issue by retrieving the agent status, run the command `systemctl status transporter-update-agent`.
`CDS_RP_108`	The update agent of the proxy client appliance hasn't started correctly. To fix the issue, run the commands `systemctl enable transporter-update-agent.timer` and `systemctl start transporter-update-agent.timer`.
`CDS_RP_109`	The MTU that is configured on the proxy client appliance is different from the actual MTU on the VM. To fix this, edit the MTU field in `/etc/docker/daemon.json` to be the same as the MTU of the VM and then run `systemctl restart docker`.
`CDS_RP_110`	The reverse proxy host that you configured isn't a valid reverse proxy host. To fix this, double check the `reverse-proxy-host` OVF property.
`CDS_RP_111`	This means there is not enough space on the disk. To fix the issue, run the command to clean up space `docker system prune -a`.
`CDS_RP_112`	This means the VM was unable to authenticate with Docker. Reach out to VMware support for further assistance.
`CDS_RP_113`	This means the VM was unable to authenticate with Docker. Reach out to VMware support for further assistance.
`CDS_RP_114`	This means accessing a transporter proxy target host was rejected because it's not an allowed target. Verify that your allowed proxy targets are configured correctly.