> For the complete documentation index, see [llms.txt](https://rubrik.gitbook.io/vcd-extension-for-rubrik/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rubrik.gitbook.io/vcd-extension-for-rubrik/getting-started/troubleshooting/plugin-connectivity.md).

# Plugin Connectivity

Connectivity to Rubrik from Cloud Director

### Self Signed Certificates

Currently, using the Nginx guide, will auto-generate some self-signed certificates. If these are not replaced with valid certificates, connectivity to Rubrik from Cloud Director will encounter `net::ERR_CERT_AUTHORITY_INVALID` errors. This is Chrome's protection when using self-signed certificates to ensure that you trust the website you are visiting.

In order to confirm and validate this is the issue, during manual authentication, or page load, you will need to open the Chrome Console and see if the messages being displayed refer to the Certificate. follow the steps below to view the console and validate these errors

* Right Click within the Chrome Window in any open space
* Select `Inspect` 
* Select the `Console` Tab
* Check for `net::ERR_CERT_AUTHORITY_INVALID`

![Console Example](https://4095106604-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LhZl1ijzJsQtWdyQE3k%2F-M3kkVyd7eGxUSoXFOVi%2F-M3klbgHksYBbpFMQhrU%2Fimage.png?alt=media\&token=2bf80d72-7c53-4a10-90c8-0c68d3683dde)

### Certificate Resolution

There are a few solutions in order to resolve this issue. 

#### Accept the Certificate

In chrome you can choose to accept the self-signed certificate as valid, however, this is temporary for the current browser session. Follow these steps to accept the certificate:

* Open a new Chrome Tab
* Enter the address of the Proxy Server e.g. `https://rubrik-proxy.rubrik.com` 
* Upon opening the page there will be a chrome error shown 
* Select `Advanced` 
* Select `Proceed to rubrik-proxy.rubrik.com`

![Certificate Error](https://4095106604-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LhZl1ijzJsQtWdyQE3k%2F-M3kkVyd7eGxUSoXFOVi%2F-M3kmQ18qh22oy4Rgn-v%2Fimage.png?alt=media\&token=9ec7bf3a-7692-4b89-b9da-8e2a0a0347d5)

* Return to the Cloud Director Plugin and Authenticate again to confirm the issue is gone

#### Install Valid Certificates

Installing Valid certificates removes all errors allowing the user to proceed unhindered. This requires the having a valid `crt` and `key` certificate file which can be updated on the nginx proxy. Refer the to Quick Start for Nginx Proxy section **Using Signed Certificates**:

{% content-ref url="/pages/-Li7w6XcjNr88QRHbvbG" %}
[Nginx Reverse Proxy](/vcd-extension-for-rubrik/getting-started/advanced-installation/quick-start-nginx-reverse-proxy.md)
{% endcontent-ref %}

#### Install the Self-Signed Certificate on the client

This is the least favorable option as this requires installing the certificate on any clients needing to use the  vCloud Director plugin. We will need to take the `crt` file from the Nginx server and install this onto the client machine as a trusted certificate. The certificate can be found here:

```
/etc/tls/crt/STAR_wildcard.crt
```