Compare commits

..

No commits in common. "92592fbfa55d07419c9b008809164a1dbb8ec29e" and "62a1c61f54244859d33d5697bb954960f130901d" have entirely different histories.

2 changed files with 5 additions and 5 deletions

View File

@ -1,6 +1,6 @@
server { server {
listen 80; listen 80;
server_name thelinuxpro.net; server_name example.org;
server_tokens off; server_tokens off;
location /.well-known/acme-challenge/ { location /.well-known/acme-challenge/ {
@ -14,7 +14,7 @@ server {
server { server {
listen 443 ssl; listen 443 ssl;
server_name thelinuxpro.net; server_name example.org;
server_tokens off; server_tokens off;
ssl_certificate /etc/letsencrypt/live/example.org/fullchain.pem; ssl_certificate /etc/letsencrypt/live/example.org/fullchain.pem;

View File

@ -5,11 +5,11 @@ if ! [ -x "$(command -v docker-compose)" ]; then
exit 1 exit 1
fi fi
domains=(thelinuxpro.net thelinux.pro git.thelinuxpro.net kameronkenny.com www.kameronkenny.com blog.kameronkenny.com) domains=(example.org www.example.org)
rsa_key_size=4096 rsa_key_size=4096
data_path="./data/certbot" data_path="./data/certbot"
email="kkenny379@gmail.com" # Adding a valid address is strongly recommended email="" # Adding a valid address is strongly recommended
staging=1 # Set to 1 if you're testing your setup to avoid hitting request limits staging=0 # Set to 1 if you're testing your setup to avoid hitting request limits
if [ -d "$data_path" ]; then if [ -d "$data_path" ]; then
read -p "Existing data found for $domains. Continue and replace existing certificate? (y/N) " decision read -p "Existing data found for $domains. Continue and replace existing certificate? (y/N) " decision