2017-02-01 15:18:37 +00:00
|
|
|
#Using deploy api
|
2017-02-09 02:02:00 +00:00
|
|
|
|
|
|
|
|
#Using the ssh deploy plugin
|
|
|
|
|
|
|
|
|
|
The ssh deploy plugin allows you to deploy certificates to a remote host
|
|
|
|
|
using SSH command to connect to the remote server. The ssh plugin is invoked
|
|
|
|
|
with the following command...
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
acme.sh --deploy -d example.com --deploy-hook ssh
|
|
|
|
|
```
|
|
|
|
|
Prior to running this for the first time you must tell the plugin where
|
|
|
|
|
and how to deploy the certificates. This is done by exporting the following
|
2017-02-09 02:13:00 +00:00
|
|
|
environment variables. This is not required for subsequent runs as the
|
2017-02-09 02:02:00 +00:00
|
|
|
values are stored by acme.sh in the domain configuration files.
|
|
|
|
|
|
|
|
|
|
Required...
|
|
|
|
|
```bash
|
|
|
|
|
export ACME_DEPLOY_SSH_USER="admin"
|
|
|
|
|
```
|
|
|
|
|
Optional...
|
|
|
|
|
```bash
|
|
|
|
|
export ACME_DEPLOY_SSH_SERVER="qnap"
|
|
|
|
|
export ACME_DEPLOY_SSH_PORT="22"
|
|
|
|
|
export ACME_DEPLOY_SSH_SERVICE_STOP=""
|
|
|
|
|
export ACME_DEPLOY_SSH_KEYFILE="/etc/stunnel/stunnel.pem"
|
|
|
|
|
export ACME_DEPLOY_SSH_CERTFILE="/etc/stunnel/stunnel.pem"
|
|
|
|
|
export ACME_DEPLOY_SSH_CAFILE="/etc/stunnel/uca.pem"
|
|
|
|
|
export ACME_DEPLOY_SSH_FULLCHAIN=""
|
|
|
|
|
export ACME_DEPLOY_SSH_REMOTE_CMD="/etc/init.d/stunnel.sh restart"
|
|
|
|
|
export ACME_DEPLOY_SSH_SERVICE_START=""
|
|
|
|
|
```
|
2017-02-09 02:13:00 +00:00
|
|
|
The values used above are illustrative only and represent those that could
|
|
|
|
|
be used to deploy certificates to a QNAP NAS device running QTS 4.2
|
2017-02-09 02:02:00 +00:00
|
|
|
|
|
|
|
|
###ACME_DEPLOY_SSH_USER
|
|
|
|
|
Username at the remote host that SSH will login with. Note that
|
|
|
|
|
SSH must be able to login to remote host without a password... SSH Keys
|
|
|
|
|
must have been exchanged with the remote host. Validate and test that you
|
|
|
|
|
can login to USER@URL from the host running acme.sh before using this script.
|
|
|
|
|
|
|
|
|
|
The USER@URL at the remote server must also have has permissions to write to
|
|
|
|
|
the target location of the certificate files and to execute any commands
|
|
|
|
|
(e.g. to stop/start services).
|
|
|
|
|
###ACME_DEPLOY_SSH_SERVER
|
|
|
|
|
URL or IP Address of the remote server. If not provided then the domain
|
|
|
|
|
name provided on the acme.sh --deploy command line is used.
|
|
|
|
|
###ACME_DEPLOY_SSH_PORT
|
|
|
|
|
Port number that SSH will attempt to connect to at the remote server. If
|
2017-02-09 02:13:00 +00:00
|
|
|
not provided then defaults to 22.
|
2017-02-09 02:02:00 +00:00
|
|
|
###ACME_DEPLOY_SSH_SERVICE_STOP
|
|
|
|
|
Command to execute on the remote server prior to copying any certificates. This
|
|
|
|
|
would typically be used to stop the service for which the certificates are
|
|
|
|
|
being deployed.
|
|
|
|
|
###ACME_DEPLOY_SSH_KEYFILE
|
2017-02-09 02:13:00 +00:00
|
|
|
Target filename for the private key issued by LetsEncrypt.
|
2017-02-09 02:02:00 +00:00
|
|
|
###ACME_DEPLOY_SSH_CERTFILE
|
2017-02-09 02:13:00 +00:00
|
|
|
Target filename for the certificate issued by LetsEncrypt. If this filename
|
|
|
|
|
is the same as that provided for ACME_DEPLOY_SSH_KEYFILE then this certificate
|
|
|
|
|
is appended to the same file as the private key.
|
2017-02-09 02:02:00 +00:00
|
|
|
###ACME_DEPLOY_SSH_CAFILE
|
2017-02-09 02:13:00 +00:00
|
|
|
Target filename for the CA intermediate certificate issued by LetsEncrypt.
|
2017-02-09 02:02:00 +00:00
|
|
|
###ACME_DEPLOY_SSH_FULLCHAIN
|
2017-02-09 02:13:00 +00:00
|
|
|
Target filename for the fullchain certificate issued by LetsEncrypt.
|
2017-02-09 02:02:00 +00:00
|
|
|
###ACME_DEPLOY_SSH_REMOTE_CMD
|
|
|
|
|
Command to execute on the remote server after copying any certificates. This
|
|
|
|
|
could be any additional command required prior to starting the service again,
|
|
|
|
|
or could be a all-inclusive restart (stop and start of service). If
|
|
|
|
|
ACME_DEPLOY_SSH_SERVICE_STOP value was provided then a 2 second sleep is
|
|
|
|
|
inserted prior to calling this command to allow the system to stabalize.
|
|
|
|
|
###ACME_DEPLOY_SSH_SERVICE_START
|
|
|
|
|
Command to execute on the remote server after copying any certificates. This
|
|
|
|
|
would typically be used to stop the service for which the certificates are
|
|
|
|
|
being deployed. If ACME_DEPLOY_SSH_SERVICE_STOP or ACME_DEPLOY_SSH_REMOTE_CMD
|
2017-02-09 02:13:00 +00:00
|
|
|
values were provided then a 2 second sleep is inserted prior to calling
|
2017-02-09 02:02:00 +00:00
|
|
|
this command to allow the system to stabalize.
|
|
|
|
|
|
|
|
|
|
##Backups
|
|
|
|
|
Before writing a certificate file to the remote server the existing
|
|
|
|
|
certificate will be copied to a backup directory on the remote server.
|
|
|
|
|
These are placed in a hidden directory in the home directory of the SSH
|
|
|
|
|
user
|
|
|
|
|
```bash
|
|
|
|
|
~/.acme_ssh_deploy/[domain name]-backup-[timestamp]
|
|
|
|
|
```
|
|
|
|
|
Any backups older than 180 days will be deleted when new certificates
|
|
|
|
|
are deployed.
|
