Updated deployhooks (markdown)
parent
f0528aa214
commit
aca2b6fa4a
|
@ -735,4 +735,32 @@ When using https to connect to the Web UI with an existing self-signed certifica
|
||||||
acme.sh --insecure --deploy -d example.com --deploy-hook peplink
|
acme.sh --insecure --deploy -d example.com --deploy-hook peplink
|
||||||
```
|
```
|
||||||
|
|
||||||
The certificate should now show up in "Network" -> "Certificate Manager".
|
The certificate should now show up in "Network" -> "Certificate Manager".
|
||||||
|
|
||||||
|
## 25. Deploy ssl cert on TrueNAS Core Server based on RestApi
|
||||||
|
|
||||||
|
Before you can deploy your cert, you must [issue the cert first](https://github.com/Neilpang/acme.sh/wiki/How-to-issue-a-cert).
|
||||||
|
If you run the acme.sh Scipt on the Truenas Server itself you have to use the --dns option.
|
||||||
|
Deploy Scipt supports TrueNas Core newer than 12.0 U3.
|
||||||
|
|
||||||
|
```sh
|
||||||
|
# Following environment variables must be set:
|
||||||
|
#
|
||||||
|
# export DEPLOY_TRUENAS_APIKEY="<API_KEY_GENERATED_IN_THE_WEB_UI"
|
||||||
|
#
|
||||||
|
# The following environmental variables may be set if you don't like their
|
||||||
|
# default values:
|
||||||
|
#
|
||||||
|
# DEPLOY_TRUENAS_HOSTNAME - defaults to localhost
|
||||||
|
# DEPLOY_TRUENAS_SCHEME - defaults to http, set alternatively to https```
|
||||||
|
|
||||||
|
```
|
||||||
|
In the WebUI from TrueNAS you can click on the gear wheel in the top right corner than select API Keys.
|
||||||
|
Here you can create an API Key for the next step.
|
||||||
|
|
||||||
|
```sh
|
||||||
|
export DEPLOY_TRUENAS_APIKEY="1-91iX3...aSTRr4xcv1FHU"
|
||||||
|
acme.sh --deploy -d truenas.example.com --deploy-hook truenas
|
||||||
|
```
|
||||||
|
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue