> ## Documentation Index
> Fetch the complete documentation index at: https://enterprise-docs.dify.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Domain and SSL Certificate

## Domain Requirements

Dify Enterprise requires 6 domains to be set up. The domains are:

* Console: console.dify.local
* Services API: api.dify.local
* APP: app.dify.local
* Files: upload.dify.local
* Enterprise: enterprise.dify.local
* Trigger: trigger.dify.local

## Find the Domain Configuration in the Helm Chart Values

### Display Helm Chart Values

```bash theme={null}
helm show values dify/dify
```

This is an example of the domain configuration in the Helm chart values.

```yaml theme={null}
global:
  consoleApiDomain: "console.dify.local"
  consoleWebDomain: "console.dify.local"
  serviceApiDomain: "api.dify.local"
  appApiDomain: "app.dify.local"
  appWebDomain: "app.dify.local"
  filesDomain: "upload.dify.local"
  enterpriseDomain: "enterprise.dify.local"
  triggerDomain: "trigger.dify.local"
  ... ...
```

## How to configure SSL Certificate

### Generate SSL Certificate

```bash theme={null}
kubectl create secret tls example-tls --key example.key --cert example.crt
```

### Update Helm values

#### Set `useTLS` to `true`

```yaml theme={null}
global:
  useTLS: true
```

#### Update Ingress values

If you only have one certificate, you can set it like this

```yaml theme={null}
ingress:
  tls: 
  - hosts:
    - console.dify.local
    - app.dify.local
    - api.dify.local
    - upload.dify.local
    - enterprise.dify.local
    - trigger.dify.local
    secretName: example-tls
```

If you have multiple certificates, you can set it like this

```yaml theme={null}
ingress:
  tls: 
  - hosts:
    - console.dify.local
    secretName: example-tls
  - hosts:
    - app.dify.local
    secretName: example-tls-2
  - hosts:
    - api.dify.local
    secretName: example-tls-3
  - hosts:
    - upload.dify.local
    secretName: example-tls-4
  - hosts:
    - enterprise.dify.local
    secretName: example-tls-5
  - hosts:
    - trigger.dify.local
    secretName: example-tls-6
```

## The cache error of Http/Https

After configuring the SSL certificate, if you encounter http/https cache errors in your browser, you can restart the Dify service to clear the cache.

```bash theme={null}
kubectl rollout restart deployment dify-api
kubectl rollout restart deployment dify-web
kubectl rollout restart deployment dify-enterprise-frontend
```