User Tools

Site Tools


procedures:certificates

This is an old revision of the document!


SSL certs renewal

FIRST THING

BACKUP THE EXISTENT CERTS (in /etc/servicepattern/)
In case anything goes wrong, you will reuse the old certs.


To install certbot:

yum install -y certbot-nginx



No acme-challenge

Istances that need certs for operation

  • Prod5_Core1(Frankfurt)
  • Prod5_Core2(Frankfurt)
  • BeCloud5x
  • Monitor
  • Be360(s)

(There are shared Outlook calendars for all expiring certs)


Commands

Certbot single istances

certbot certonly --nginx


Certbot clusters

For clusters, you need to run the command on both “Core” istances, but first you have to modify the “weight” of the domain. Login to AWS DNS and select the desired Hosted Zone.

Clusters have shared domain between two machines (for example, Prod5_Core1 and Prod5_Core2 are both pointed by *beincontact.becloudsolutions.com*), to change the weight select one of the two record entry, on the left panel click “Edit record”, change the param “Weight” from 100 to 0, then save.

You have to do this for the machine where you are not trying to renew the certificates (for example, you want to renew Prod5_Core1, change the param of Prod5_Core2, renew the 1 and then convert everything to renew the 2), then restore the weight and repeat the process for the second server.

certbot certonly --nginx -d **domain**,**domain**,*etc*

Copy-paste domains Core1:

-d core1.beincontact.becloudsolutions.com,beincontact.becloudsolutions.com,elettric80.beincontact.becloudsolutions.com,prysmianuk.beincontact.becloudsolutions.com,prysmianib.beincontact.becloudsolutions.com,alidays.beincontact.becloudsolutions.com,aria.beincontact.becloudsolutions.com,beeasy.beincontact.becloudsolutions.com,prysmianfr.beincontact.becloudsolutions.com,fives.beincontact.becloudsolutions.com,medicair.beincontact.becloudsolutions.com,golilla.beincontact.becloudsolutions.com,excellgo.beincontact.becloudsolutions.com,newtime.beincontact.becloudsolutions.com,aetnagroup.beincontact.becloudsolutions.com

Copy-paste domains Core2:

-d core2.beincontact.becloudsolutions.com,beincontact.becloudsolutions.com,elettric80.beincontact.becloudsolutions.com,prysmianuk.beincontact.becloudsolutions.com,prysmianib.beincontact.becloudsolutions.com,alidays.beincontact.becloudsolutions.com,aria.beincontact.becloudsolutions.com,beeasy.beincontact.becloudsolutions.com,prysmianfr.beincontact.becloudsolutions.com,fives.beincontact.becloudsolutions.com,medicair.beincontact.becloudsolutions.com,golilla.beincontact.becloudsolutions.com,excellgo.beincontact.becloudsolutions.com,newtime.beincontact.becloudsolutions.com,aetnagroup.beincontact.becloudsolutions.com


Certbot not installed

./certbot-auto certonly --nginx

(if you don't find the script you can locate it with find / -iname certbot-auto)

Follow the wizard and read the final output, you need to cd into the directory of the certificate before running the commands to preare the certs (will be in /etc/letsencrypt/live/)



Acme-challenge

Istances that need certs for operation

  • Prod5_Core1(Sydney)
  • Prod5_Core2(Sydney)

(There are shared Outlook calendars for all expiring certs)


Commands

Acme-challenges clusters

For clusters, you need to run the command on both “Core” istances, but first you have to modify the “weight” of the domain. Login to AWS DNS and select the desired Hosted Zone.

Clusters have shared domain between two machines (for example, Prod5_Core1 and Prod5_Core2 are both pointed by *beincontact.becloudsolutions.com*), to change the weight select one of the two record entry, on the left panel click “Edit record”, change the param “Weight” from 100 to 0, then save.

You have to do this for the machine where you are not trying to renew the certificates (for example, you want to renew Prod5_Core1, change the param of Prod5_Core2, renew the 1 and then convert everything to renew the 2), then restore the weight and repeat the process for the second server.

Follow the instructions on screen and replace old entries in the DNS, make a copy of the old values in case you need to use the old certs. Do not create multiple records for one domain, even if certbot tell you to do it, you can't in AWS.

certbot certonly --manual --preferred-challenges dns --key-type rsa -d **domain**,**domain**,*etc*

Copy-paste domains:

-d beincontact2.becloudsolutions.com,core1.beincontact2.becloudsolutions.com,core2.beincontact2.becloudsolutions.com,prysmianau.beincontact2.becloudsolutions.com,humecity.beincontact2.becloudsolutions.com,benetas.beincontact2.becloudsolutions.com


Follow the wizard and read the final output, you need to cd into the directory of the certificate before running the commands to preare the certs (will be in /etc/letsencrypt/live/)


Certs preparation

cp privkey.pem server.key
cat fullchain.pem | cat - privkey.pem > server.pem
\cp -b server.key /etc/servicepattern/
\cp -b server.pem /etc/servicepattern/


Restart services

systemctl restart nginx && systemctl restart agentserver


Lorenzo Cesana 2024/09/02 08:58

procedures/certificates.1729279159.txt.gz · Last modified: by sysadm

Except where otherwise noted, content on this wiki is licensed under the following license: Public Domain
Public Domain Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki