mirror/XenOrchestraInstallerUpdater
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Updated Home (markdown)

Roni Väyrynen
2022-07-29 14:28:21 +03:00
parent e925702a00
commit d5e7ba4022
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
Home.md

@@ -12,17 +12,17 @@ cp sample.xo-install.cfg xo-install.cfg
There's few different ways to enable HTTPS for Xen Orchestra.
#### Let's Encrypt, automatically created by Xen Orchestra
#### ACME (eq. Let's Encrypt), automatically created by Xen Orchestra
Edit `xo-install.cfg` with your preferred text editor and make sure following variables are set:
```
LETSENCRYPT="true"
LETSENCRYPT_DOMAIN="your.domain.tld"
ACME="true"
ACME_DOMAIN="your.domain.tld"
```
Additionally you can set `LETSENCRYPT_EMAIL="your@email.tld"` to receive notifications related to your certificate.
Additionally you can set `ACME_EMAIL="your@email.tld"` to receive notifications related to your certificate.
Enabling Let's Encrypt overwrites some other configuration options so that it works properly, these are:
Enabling ACME overwrites some other configuration options so that it works properly, these are:
- PORT is set to 80
- AUTOCERT is set to true
@@ -33,7 +33,7 @@ Certificate will be generated when XO is accessed first time from browser with d
Check these if certificate generation doesn't work properly:
- XO instance needs to be publicly accessible with domain and ports 80/443 allowed for certificate generation to work.
- If certificate/key paths were set before and there are existing files, XO won't generate a new Let's Encrypt certificate. Stop xo-server, remove/rename these files and restart xo-server.
- If certificate/key paths were set before and there are existing files, XO won't generate a new ACME certificate. Stop xo-server, remove/rename these files and restart xo-server.
#### Self-signed certificate, automatically created by Xen Orchestra