-
Notifications
You must be signed in to change notification settings - Fork 27
/
certbot.sh
executable file
·96 lines (79 loc) · 3.68 KB
/
certbot.sh
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
#!/bin/bash
#colors
RED='\033[0;31m'
GREEN='\033[0;32m'
NC='\033[0m' # No Color
#maximum number of retries
MAXRETRIES=5
#timeout
TIMEOUT=5
printf "${GREEN}Docker Flow: Let's Encrypt started${NC}\n";
printf "We will use $CERTBOT_EMAIL for certificate registration with certbot. This e-mail is used by Let's Encrypt when you lose the account and want to get it back.\n";
#common arguments
args=("--no-self-upgrade" "--no-bootstrap" "--standalone" "--non-interactive" "--expand" "--keep-until-expiring" "--email" "$CERTBOT_EMAIL" "--agree-tos" "--preferred-challenges" "http-01" "--rsa-key-size" "4096" "--redirect" "--hsts" "--staple-ocsp")
#if we are in a staging enviroment append the staging argument, the staging argument
#was previously set to an empty string if the staging enviroment was not used
#but this confuses cert-auto and should hence not be used
if [ "$CERTBOTMODE" ]; then
printf "${RED}Staging environment of Let's Encrypt is activated! The generated certificates won't be trusted. But you will not reach Let’s Encrypt's rate limits.${NC}\n";
args+=("--staging");
fi
#we need to be careful and don't reach the rate limits of Let's Encrypt https://letsencrypt.org/docs/rate-limits/
#Let's Encrypt has a certificates per registered domain (20 per week) and a names per certificate (100 subdomains) limit
#so we should create ONE certificiates for a certain domain and add all their subdomains (max 100!)
for var in $(env | grep -P 'DOMAIN_\d+' | sed -e 's/=.*//'); do
cur_domains=${!var};
declare -a arr=$cur_domains;
DOMAINDIRECTORY="/etc/letsencrypt/live/${arr[0]}";
dom="";
for i in "${arr[@]}"
do
let validated=tries=0
until [ $tries -ge $MAXRETRIES ]
do
tries=$[$tries+1]
certbot certonly --dry-run "${args[@]}" -d "$i" | grep -q 'The dry run was successful.'
if [ $? -eq 0 ]; then
validated=1
break
else
if [ $tries -eq $MAXRETRIES ]; then
printf "${RED}Unable to verify domain ownership after ${tries} attempts.${NC}\n"
else
printf "${RED}Unable to verify domain ownership, we try again in ${TIMEOUT} seconds.${NC}\n"
sleep $TIMEOUT
fi
fi
done
echo "Validated is $validated"
if [ $validated -eq 1 ]; then
printf "Domain $i successfully validated\n"
dom="$dom -d $i"
fi
done
#only if we have successfully validated at least a single domain we have to continue
if [ -n "$dom" ]; then
# check if DOMAINDIRECTORY exists, if it exists use --cert-name to prevent 0001 0002 0003 folders
if [ -d "$DOMAINDIRECTORY" ]; then
printf "\nUse certbot certonly %s --cert-name %s\n" "${args[*]}" "${arr[0]}";
certbot certonly "${args[@]}" --cert-name "${arr[0]}" $dom
else
printf "\nUse certbot certonly %s\n" "${args[*]}";
certbot certonly "${args[@]}" $dom
fi
fi
done
#prepare renewcron
if [ "$CERTBOTMODE" ]; then
printf "SHELL=/bin/sh\nPATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin\nPROXY_ADDRESS=$PROXY_ADDRESS\nCERTBOTMODE=$CERTBOTMODE\n" > /etc/cron.d/renewcron
else
printf "SHELL=/bin/sh\nPATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin\nPROXY_ADDRESS=$PROXY_ADDRESS\n" > /etc/cron.d/renewcron
fi
declare -a arr=$CERTBOT_CRON_RENEW;
for i in "${arr[@]}"
do
printf "$i root /root/renewAndSendToProxy.sh > /var/log/dockeroutput.log\n" >> /etc/cron.d/renewcron
done
printf "\n" >> /etc/cron.d/renewcron
#run renewAndSendToProxy script which calls certbot renew (yeah, certbot will be run again but this isn't a problem. In fact this script is also run via cron and therefore we must call certbot renew), concatenates the certificates and sends them to the proxy
/root/renewAndSendToProxy.sh