diff --git a/Production/README.md b/Production/README.md index 034c339..eea068b 100644 --- a/Production/README.md +++ b/Production/README.md @@ -20,7 +20,7 @@ The relevant environment variables are: * `BTCPAY_HOST`: The external url used to access the NGINX server from internet. This domain name must point to this machine for Let's Encrypt to create your certificate. (typically with a CNAME or A record) * `BTCPAY_ROOTPATH`: The root path directory where BTCPay is accessed, more information below. (default: /) * `LETSENCRYPT_EMAIL`: The email Let's Encrypt will use to notify you about certificate expiration. -* `ACME_CA_URI`: Let's encrypt API endpoint (`https://acme-staging.api.letsencrypt.org/directory` for a staging certificate, `https://acme-v01.api.letsencrypt.org/directory` for a production one) +* `ACME_CA_URI`: Let's encrypt API endpoint (`https://acme-staging.api.letsencrypt.org/directory` for a staging certificate, `https://acme-v02.api.letsencrypt.org/directory` for a production one) * `LIGHTNING_ALIAS`: Optional, if using the integrated lightning feature, customize the alias of your nodes * `BTCPAY_SSHKEYFILE`: Optional, SSH private key that BTCPay can use to connect to this VM's SSH server (You need to copy the key file on BTCPay's datadir volume) * `BTCPAY_SSHTRUSTEDFINGERPRINTS`: Optional, BTCPay will ensure that it is connecting to the expected SSH server by checking the host public's key against those fingerprints @@ -45,7 +45,7 @@ docker-compose up \ -e "NBITCOIN_NETWORK=mainnet" \ -e "BTCPAY_HOST=btcpay.example.com" \ -e "LETSENCRYPT_EMAIL=me@example.com" \ - -e "ACME_CA_URI=https://acme-v01.api.letsencrypt.org/directory" + -e "ACME_CA_URI=https://acme-v02.api.letsencrypt.org/directory" ``` For powershell: @@ -55,7 +55,7 @@ docker-compose up ` -e "NBITCOIN_NETWORK=mainnet" ` -e "BTCPAY_HOST=btcpay.example.com" ` -e "LETSENCRYPT_EMAIL=me@example.com" ` - -e "ACME_CA_URI=https://acme-v01.api.letsencrypt.org/directory" + -e "ACME_CA_URI=https://acme-v02.api.letsencrypt.org/directory" ``` See also [The guide for docker noobs](../README.md#fornoobs). diff --git a/README.md b/README.md index 455cd5d..0636931 100644 --- a/README.md +++ b/README.md @@ -104,7 +104,7 @@ You can read [the article](https://medium.com/@BtcpayServer/hosting-btcpay-serve * `BTCPAYGEN_SUBNAME`: The subname of the generated docker-compose file, where the full name is `Generated/docker-compose.SUBNAME.yml` (Default: `generated`) * `BTCPAYGEN_ADDITIONAL_FRAGMENTS`: Semicolon-separated list of additional fragments you want to use (eg. `opt-save-storage`) * `LETSENCRYPT_EMAIL`: An email will be sent to this address if certificate expires and fails to renew automatically (eg. `me@example.com`) -* `ACME_CA_URI`: The API endpoint to ask for HTTPS certificate (Default: `https://acme-v01.api.letsencrypt.org/directory`) +* `ACME_CA_URI`: The API endpoint to ask for HTTPS certificate (Default: `https://acme-v02.api.letsencrypt.org/directory`) * `BTCPAY_ENABLE_SSH`: Optional, gives BTCPay Server SSH access to the host by allowing it to edit authorized_keys of the host, it can be used for managing the authorized_keys or updating BTCPay Server directly through the website. (Default: false) * `BTCPAYGEN_DOCKER_IMAGE`: Optional, Specify which generator image to use if you have customized the C# generator. Set to `btcpayserver/docker-compose-generator:local` to build the generator locally at runtime. * `BTCPAY_IMAGE`: Optional, Specify which btcpayserver image to use if you have a customized btcpayserver. @@ -262,7 +262,7 @@ WantedBy=multi-user.target ```ini BTCPAY_HOST=btcpay.EXAMPLE.com -ACME_CA_URI=https://acme-v01.api.letsencrypt.org/directory +ACME_CA_URI=https://acme-v02.api.letsencrypt.org/directory NBITCOIN_NETWORK=mainnet LETSENCRYPT_EMAIL=me@EXAMPLE.com BTCPAY_SSHTRUSTEDFINGERPRINTS=SHA256:eSCD7NtQ/Q6IBl2iRB9caAQ3lDZd8s8iUL6SdeNnhpA diff --git a/btcpay-setup.sh b/btcpay-setup.sh index d597305..4e5e68d 100755 --- a/btcpay-setup.sh +++ b/btcpay-setup.sh @@ -93,7 +93,7 @@ Environment variables: BTCPAYGEN_REVERSEPROXY: Whether to use or not a reverse proxy. NGinx setup HTTPS for you. (eg. nginx, traefik, none. Default: nginx) BTCPAYGEN_LIGHTNING: Lightning network implementation to use (eg. clightning, lnd, none) BTCPAYGEN_ADDITIONAL_FRAGMENTS: Semi colon separated list of additional fragments you want to use (eg. opt-save-storage) - ACME_CA_URI: The API endpoint to ask for HTTPS certificate (default: https://acme-v01.api.letsencrypt.org/directory) + ACME_CA_URI: The API endpoint to ask for HTTPS certificate (default: https://acme-v02.api.letsencrypt.org/directory) BTCPAY_ENABLE_SSH: Optional, gives BTCPay Server SSH access to the host by allowing it to edit authorized_keys of the host, it can be used for managing the authorized_keys or updating BTCPay Server directly through the website. (Default: false) BTCPAYGEN_DOCKER_IMAGE: Allows you to specify a custom docker image for the generator (Default: btcpayserver/docker-compose-generator) BTCPAY_IMAGE: Allows you to specify the btcpayserver docker image to use over the default version. (Default: current stable version of btcpayserver) @@ -194,7 +194,7 @@ fi : "${BTCPAYGEN_REVERSEPROXY:=nginx}" : "${BTCPAYGEN_LIGHTNING:=none}" : "${REVERSEPROXY_DEFAULT_HOST:=none}" -: "${ACME_CA_URI:=https://acme-v01.api.letsencrypt.org/directory}" +: "${ACME_CA_URI:=https://acme-v02.api.letsencrypt.org/directory}" : "${BTCPAY_PROTOCOL:=https}" : "${BTCPAY_ADDITIONAL_HOSTS:=}" : "${REVERSEPROXY_HTTP_PORT:=80}" diff --git a/changedomain.sh b/changedomain.sh index 9d990c2..45361cd 100755 --- a/changedomain.sh +++ b/changedomain.sh @@ -11,7 +11,7 @@ export OLD_HOST=`cat $BTCPAY_ENV_FILE | sed -n 's/^BTCPAY_HOST=\(.*\)$/\1/p'` echo "Changing domain from \"$OLD_HOST\" to \"$NEW_HOST\"" export BTCPAY_HOST="$NEW_HOST" -export ACME_CA_URI="https://acme-v01.api.letsencrypt.org/directory" +export ACME_CA_URI="https://acme-v02.api.letsencrypt.org/directory" [[ "$OLD_HOST" == "$REVERSEPROXY_DEFAULT_HOST" ]] && export REVERSEPROXY_DEFAULT_HOST="$NEW_HOST" pushd . > /dev/null # Modify environment file