Difference between revisions of "Letsencrypt/fr"

'IMPORTANT'

# config show modSSL

modSSL=service
    TCPPort=443
    access=public
    status=enabled

config show modSSL > "/root/db_configuration_modSSL_backup_$(date +%Y%m%d_%H%M%S)"

yum install smeserver-letsencrypt --enablerepo=smecontribs

config setprop letsencrypt ACCEPT_TERMS yes
signal-event console-save

yum update smeserver-letsencrypt dehydrated --enablerepo=smecontribs

signal-event post-upgrade;  signal-event reboot

signal-event console-save

db domains setprop $DOMAINE letsencryptSSLcert enabled

db domains setprop domaine1.com  letsencryptSSLcert enabled

db hosts setprop $NOM_D_HOTE letsencryptSSLcert enabled

db hosts setprop www.domaine1.com letsencryptSSLcert enabled

config setprop letsencrypt configure domains

config setprop letsencrypt configure hosts

config setprop letsencrypt configure all

config setprop letsencrypt configure none

 config setprop letsencrypt email admin@domaine1.com

config setprop letsencrypt keysize NOMBRE

config setprop letsencrypt ACCEPT_TERMS yes

config setprop letsencrypt status test
signal-event console-save

dehydrated -c

config setprop letsencrypt status enabled
signal-event console-save

dehydrated -c -x

# config show letsencrypt
letsencrypt=service
   ACCEPT_TERMS=yes
   API=1
   configure=none
   email=####@#####.###
   hookScript=disabled
   status=enabled

# config setprop letsencrypt API 2 
# signal-event console-save

# config show letsencrypt
letsencrypt=service
   ACCEPT_TERMS=yes
   API=2
   configure=none
   email=####@#####.###
   hookScript=disabled
   status=enabled

# dehydrated -c -x

dehydrated --cleanup (-gc)

 config setprop letsencrypt ACCEPT_TERMS yes status test API 2
 #pour chacun de vos domaines où vous voulez SSL, faire ce qui suit :
 db domains setprop domaine1.com letsencryptSSLcert enabled
 #pour chacun de vos hôtes (sous-domaines) où vous voulez SSL, faire ce qui suit :
 db hosts setprop www.domaine1.com letsencryptSSLcert enabled
 signal-event console-save
 dehydrated -c

config setprop letsencrypt status enabled email admin@domaine1.com
signal-event console-save
dehydrated -c -x

yum --enablerepo=smecontribs install dehydrated

yum install git

cd /etc
git clone https://github.com/lukas2511/dehydrated
mv dehydrated/dehydrated /usr/local/bin/

cd /etc/dehydrated
mkdir -p /home/e-smith/files/ibays/Primary/html/.well-known/acme-challenge
nano -w domains.txt

domain1.com www.domain1.com mail.domain1.com domain2.net www.domain2.net domain3.org ftp.domain3.org

nano -w config

#!/bin/bash
# config
# CA="https://acme-staging.api.letsencrypt.org/directory"
WELLKNOWN="/home/e-smith/files/ibays/Primary/html/.well-known/acme-challenge"
HOOK="/usr/local/bin/dehydrated-hook"
# E-mail to use during the registration (default: <unset>)
CONTACT_EMAIL="admin@yourdomain.com"

nano /usr/local/bin/dehydrated-hook

#!/bin/bash

if [ $1 = "deploy_cert" ]; then
  KEY=$3
  CERT=$4
  CHAIN=$6
  /sbin/e-smith/db configuration setprop modSSL key $KEY
  /sbin/e-smith/db configuration setprop modSSL crt $CERT
  /sbin/e-smith/db configuration setprop modSSL CertificateChainFile $CHAIN
  /sbin/e-smith/signal-event ssl-update
fi

chmod +x /usr/local/bin/dehydrated-hook

mkdir -p /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf
nano -w /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/VirtualHosts40ACME

# Alias for letsencrypt
Alias /.well-known/acme-challenge /home/e-smith/files/ibays/Primary/html/.well-known/acme-challenge

expand-template /etc/httpd/conf/httpd.conf
service httpd-e-smith restart

dehydrated -c

config show modSSL

dehydrated -c -x

nano -w /etc/cron.daily/call-dehydrated

#!/bin/bash
/usr/bin/dehydrated -c
Ctrl-X pour quitter, Y pour sauvegarder. Ensuite, rendez-le exécutable :
chmod +x /etc/cron.daily/call-dehydrated

db accounts setprop {accountname} SSL enabled

db accounts setprop Primary SSL enabled

Include=/etc/dehydrated

config setprop modSSL crt (old value)
config setprop modSSL key (old value)
config setprop modSSL CertificateChainFile (old value--if this property was empty, delete it using the command line below)

config delprop modSSL crt
config delprop modSSL key
config delprop modSSL CertificateChainFile 

signal-event post-upgrade
signal-event reboot

/etc/dehydrated/config
/etc/dehydrated/domains.txt

db configuration setprop letsencrypt status test

rm /etc/dehydrated/certs/* -rf
rm /etc/dehydrated/accounts/* -rf

dehydrated -c

config delprop modSSL CertificateChainFile
config delprop modSSL crt
config delprop modSSL key

signal-event console-save

{"type":"urn:acme:error:unauthorized","detail":"No registration exists matching provided key","status":403}

{"type":"urn:acme:error:rateLimited","detail":"Error creating new authz :: Too many currently pending authorizations.","status":429}

config setprop letsencrypt configure all

config setprop letsencrypt configure none

db domains setprop domain1.com letsencryptSSLcert enabled

db hosts setprop www.domain1.com letsencryptSSLcert enabled

db hosts setprop mail.domain1.com letsencryptSSLcert enabled

signal-event console-save

ERROR: Challenge is invalid! (returned: invalid) (result: {
 "type": "http-01",
 "status": "invalid",
 "error": {
   "type": "urn:acme:error:unauthorized",
   "detail": "Invalid response from http://www.your-domain.com/.well-known/acme-challenge/<redacted text>
   "status": 403

(13)Permission denied: access to /.well-known/acme-challenge/<redacted> denied
(13)Permission denied: access to /.well-known/acme-challenge/<redacted> denied
(13)Permission denied: access to /.well-known/acme-challenge/<redacted> denied

cd /home/e-smith/files/ibays

ls -l

total 4
drwxr-xr-x 5 root root 4096 Jul 25  2016 Primary

chown root:root Primary

chmod 0755 Primary

cd /home/e-smith/files/ibays/Primary

ls -l

[root@backupserver Primary]# ls -l
total 12
drwxr-s--- 2 admin shared 4096 Jul 25  2016 cgi-bin
drwxr-s--- 2 admin shared 4096 Jul 25  2016 files
drwxr-s--- 3 admin shared 4096 Jun 11 08:06 html

chown admin:shared html

chmod 2750 html

dehydrated -c

mkdir -p /etc/e-smith/templates-custom/etc/dehydrated/domains.txt
nano -w /etc/e-smith/templates-custom/etc/dehydrated/domains.txt/15Hostname

nom_d_hote.domaine

mkdir -p /etc/e-smith/templates-custom/usr/bin/hook-script.sh/
nano -w 05deploy_cert_hostname

{
    use strict;
    use warnings;
    use esmith::ConfigDB;

    my $configDB = esmith::ConfigDB->open_ro or die("can't open Config DB");

    my $letsencryptStatus = $configDB->get_prop( 'letsencrypt', 'status' )     || 'disabled';

    if ( $letsencryptStatus ne 'disabled' ) {

    $OUT .=<<'_EOF';
if [ $1 = "deploy_cert" ] && [ $2 = "hostname.domain.tld" ]; then
 echo "$2 certificate renewed" | mail -s "Certificate renewal" admin@yourdomain.com
 exit 0
fi
_EOF

    }
}

{
    use strict;
    use warnings;
    use esmith::ConfigDB;

    my $configDB = esmith::ConfigDB->open_ro or die("can't open Config DB");

    my $letsencryptStatus = $configDB->get_prop( 'letsencrypt', 'status' )     || 'disabled';

    if ( $letsencryptStatus ne 'disabled' ) {

    $OUT .=<<'_EOF';
if [ $1 = "deploy_cert" ] && [ $2 = "hostname.domain.tld" ]; then
  KEY=$3
  CERT=$4
  CHAIN=$6
  scp $CERT root@hostname:/etc/pki/tls/certs/pbx.familybrown.org.crt
  scp $KEY root@hostname:/etc/pki/tls/private/pbx.familybrown.org.key
  scp $CHAIN root@hostname:/etc/pki/tls/certs/server-chain.crt
  ssh root@pbx "/sbin/service httpd reload"
  echo "$2 certificate renewed" | mail -s "Certificate renewal" admin@domain.tld
  exit 0
fi
_EOF

    }
}

{
    use strict;
    use warnings;
    use esmith::ConfigDB;

    my $configDB = esmith::ConfigDB->open_ro or die("can't open Config DB");

    my $letsencryptStatus = $configDB->get_prop( 'letsencrypt', 'status' )     || 'disabled';

    if ( $letsencryptStatus ne 'disabled' ) {

    $OUT .=<<'_EOF';
if [ $1 = "deploy_cert" ] && [ $2 = "pve.domain.tld" ]; then
  KEY=$3
  CHAIN=$5
  scp $KEY root@pve:/etc/pve/nodes/pve/pveproxy-ssl.key
  scp $CHAIN root@pve:/etc/pve/nodes/pve/pveproxy-ssl.pem
  ssh root@pve "systemctl restart pveproxy"
  echo "$2 certificate renewed" | mail -s "Certificate renewal" admin@domain.tld
  exit 0
fi
_EOF

    }
}

signal-event console-save
dehydrated -c

config setprop letsencrypt hookScript enabled
config setprop letsencrypt host passerelle.mon-domaine.com
config setprop letsencrypt user root
config setprop letsencrypt path /home/e-smith/files/ibays/Primary/html/.well-known/acme-challenge
signal-event console-save

@@ Line 3: / Line 3: @@
 ==Introduction==
-{{warning box|type=Attention| The original protocol used by Let’s Encrypt for certificate issuance and management is called ACMEv1. In March of 2018 Letsencrypt introduced support for ACMEv2, a newer version of the protocol that matches what was finalized today as RFC 8555 328. They have been encouraging subscribers to move to the ACMEv2 protocol.
+{{warning box|type=Attention !| Le protocole original utilisé par Let’s Encrypt pour l’émission et la gestion des certificats est appelé ACMEv1. En mars 2018, Letsencrypt a introduit le support pour ACMEv2, une version plus récente du protocole qui correspond à ce qui a été finalisé aujourd'hui sous la RFC 8555 328. Ils encouragent les abonnés à passer au protocole ACMEv2.
-In March 2019 they announced an end of life plan for ACMEv1.
+En mars 2019, ils ont annoncé un plan de fin de vie pour ACMEv1.
-In November of 2019 they will stop allowing new account registrations through their ACMEv1 API endpoint. '''IMPORTANTLY''' Existing accounts will continue to function normally.
+En novembre 2019, ils ne permettront plus les nouvelles inscriptions de compte via leur point de terminaison API ACMEv1. '' 'IMPORTANT' '' Les comptes existants continueront à fonctionner normalement.
-In June of 2020 they will stop allowing new domains to validate via ACMEv1.
+En juin 2020, ils ne permettront plus aux nouveaux domaines d'être validés via ACMEv1.
-Starting at the beginning of 2021 they will occasionally disable ACMEv1 issuance and renewal for periods of 24 hours, no more than once per month (OCSP service will not be affected). The intention is to induce client errors that might encourage subscribers to update to clients or configurations that use ACMEv2.
+À compter du début de 2021, ils désactiveront occasionnellement l'émission et le renouvellement d'ACMEv1 pour des périodes de 24 heures, pas plus d'une fois par mois (le service OCSP ne sera pas affecté). Le but est d’induire des erreurs client susceptibles d’encourager les abonnés à se mettre à jour vers des clients ou des configurations utilisant ACMEv2.
-Renewal failures should be limited since new domain validations will already be disabled and we recommend renewing certificates 30 days before they expire.
+Les échecs de renouvellement doivent être limités car les nouvelles validations de domaine seront déjà désactivées et nous recommandons de renouveler les certificats 30 jours avant leur expiration.
-In June of 2021 they will entirely disable ACMEv1 as a viable way to get a Let’s Encrypt certificate.}}
+En juin 2021, ils désactiveront complètement ACMEv1 en tant que moyen viable d’obtenir un certificat Let’s Encrypt.}}
 [https://letsencrypt.org/ Let’s Encrypt] est une nouvelle Autorité de Certification (CA) :

ID	Product	Version	Status	Summary (10 tasks) ⇒
12325	SME Contribs	10.0	CONFIRMED	renewal fails after domain deleted from manager.
11796	SME Contribs	Futur	CONFIRMED	Is the dns-01 Challenge Supported or is it in planing?
11442	SME Contribs	10alpha	CONFIRMED	multiple fragments related to some other bugs
10920	SME Contribs	10alpha	CONFIRMED	move .well-known/acme-challenge out of the Primary ibay
10836	SME Contribs	9.2	CONFIRMED	force migration from acme-v1 to acme-v2
10818	SME Contribs	9.2	CONFIRMED	template does not respect domain-deleted
10656	SME Contribs	9.2	CONFIRMED	No letsencrypt certificate for Internet enable password protected Ibay
10483	SME Contribs	9.2	CONFIRMED	renewal fails with ibay using password
10462	SME Contribs	Futur	CONFIRMED	NFR: implement per certificate / domain
10280	SME Contribs	9.2	CONFIRMED	add test for domain and host to disable the one at least defined in publicly available dns

	Skill level: Medium
	The instructions on this page require a basic knowledge of linux.

	Attention :
	les éléments suivants ne doivent pas être exécutés si vous avez installé le paquet de la contribution smeserver-letsencrypt car cela est déjà géré par la contribution.

	Attention :
	fin de l'installation et de la configuration manuelles de «dehydrated» sans la contribution smeserver-letsencrypt.

	Note :
	ceci nécessite d'être testé et vérifié.

Difference between revisions of "Letsencrypt/fr"

Revision as of 18:59, 24 November 2019

Introduction

Version

Prérequis

Préparation

Installation de la contribution de Dehydrated

Installation

Mises à jour

Ré-actualisation

Configuration

Hôtes et domaines du certificat

Autres paramètres de configuration

Accepter les conditions de Let's Encrypt

Activer le mode test

Activer le mode production

V2 API

Archiver les vieux certificats

Exemples de démarrage rapide

Installation manuelle de « Dehydrated »

Installation du paquet «dehydrated» à partir du dépôt smecontrib

Installation de la dernière version de git

Configuration manuelle de «Dehydrated»

Renouvellement

Imposer le SSL

Sauvegarde

Troubleshooting

Certificate Errors

Authorization Errors

Errors

No registration exists matching provided key

rateLimited, Too many currently pending Authorizations

Some challenges complete successfully but some hostnames fail

Challenge fails with unauthorized 403 error

Sujets avancés

Obtention de certificats pour d'autres serveurs

Obtenir des certificats pour un serveur KOOZALI SME privé

Bogues

Changelog

Navigation menu

Search