# Https://bap.a3a-architecture.fr/ **URL:** \ **Category:** Aide (en français)\ **Created:** [November 7, 2024, 10:26am UTC](https://community.letsencrypt.org/t/https-bap-a3a-architecture-fr/228385 "2024-11-07T10:26:22Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Mic](https://avatars.discourse-cdn.com/v4/letter/m/e0b2c6/32.png) [@Mic](https://community.letsencrypt.org/u/Mic)\ **Post date:** [November 7, 2024, 10:26am UTC](https://community.letsencrypt.org/t/https-bap-a3a-architecture-fr/228385/1 "2024-11-07T10:26:22Z")
Bonjour à tous, j'ai un souci de renouvellement de certificat sur le site [https://bap.a3a-architecture.fr/](https://bap.a3a-architecture.fr/) la commande ci dessous m'indique à priori que tout est ok admin$ sudo certbot renew --dry-run --cert-name [bap.a3a-architecture.fr](http://bap.a3a-architecture.fr) Password: Saving debug log to /var/log/letsencrypt/letsencrypt.log * * * Processing /etc/letsencrypt/renewal/bap.a3a-architecture.fr.conf * * * Simulating renewal of an existing certificate for [bap.a3a-architecture.fr](http://bap.a3a-architecture.fr) * * * Congratulations, all simulated renewals succeeded: /etc/letsencrypt/live/bap.a3a-architecture.fr/fullchain.pem (success) Pourtant le certificat est toujours en date d'expiration au 30/10/2024 et sur Chrome Safari ou Firefox il apparait comme non sécurisé. De plus comment renouivller automatiquement ce certificat Let's encrypt, je n'ai pas réussi à mettre en oeuvre la commande. Merci de votre aide ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [November 7, 2024, 11:34am UTC](https://community.letsencrypt.org/t/https-bap-a3a-architecture-fr/228385/2 "2024-11-07T11:34:12Z")
> [@Mic](#): > > Pourtant le certificat est toujours en date d'expiration au 30/10/2024 et sur Chrome Safari ou Firefox il apparait comme non sécurisé. Habituellement, je dirais : c'est normal, car vous utilisez l'option `--dry-run`. Si vous exécutez à nouveau Certbot sans cette option, vous renouvellerez votre certificat « pour de vrai » au lieu d'utiliser l'environnement de test. Cependant, en regardant [crt.sh | 15248930267](https://crt.sh/?id=15248930267), je vois que vous avez effectivement renouvelé votre certificat ce matin (vous pouvez vérifier en exécutant `certbot certificates`. Quelle était la commande _initiale_ avec laquelle vous avez obtenu votre premier certificat ? Translated from English with Google Translate. Aussi: Veuillez remplir les champs ci-dessous pour que nous puissions vous aider. Remarque : vous devez fournir votre nom de domaine pour obtenir de l’aide. Les noms de domaine des certificats émis sont tous rendus publics dans les journaux de Transparence de Certificat (par exemple, [crt.sh | example.com](https://crt.sh/?q=example.com)). Par conséquent, le fait de ne pas indiquer votre nom de domaine ici n’aide pas à le garder secret, mais rend plus difficile pour nous le fait de vous aider. Je peux lire des réponses en Anglais : Mon nom de domaine est : J’ai exécuté cette commande : Elle a produit cette sortie : Mon serveur Web est (inclure la version) : Le système d’exploitation sur lequel mon serveur Web s’exécute est (version incluse) : Mon hébergeur, le cas échéant, est : Je peux me connecter à un shell root sur ma machine (oui ou non, ou je ne sais pas) : J’utilise un panneau de configuration pour gérer mon site (non, ou fournit le nom et la version du panneau de configuration) : ---
**Author:** ![Mic](https://avatars.discourse-cdn.com/v4/letter/m/e0b2c6/32.png) [@Mic](https://community.letsencrypt.org/u/Mic)\ **Post date:** [November 7, 2024, 1:23pm UTC](https://community.letsencrypt.org/t/https-bap-a3a-architecture-fr/228385/3 "2024-11-07T13:23:21Z")
Merci Osiris J'ai passé la commande sans dry run (sudo certbot renew --cert-name [bap.a3a-architecture.fr](http://bap.a3a-architecture.fr)) et j’obtiens ceci : sudo certbot renew --cert-name [bap.a3a-architecture.fr](http://bap.a3a-architecture.fr) Password: Saving debug log to /var/log/letsencrypt/letsencrypt.log * * * Processing /etc/letsencrypt/renewal/bap.a3a-architecture.fr.conf * * * Certificate not yet due for renewal * * * The following certificates are not due for renewal yet: /etc/letsencrypt/live/bap.a3a-architecture.fr/fullchain.pem expires on 2025-02-05 (skipped) No renewals were attempted. De ce que je comprends pas de renouvellement attendu avant 05/02/25 et pourtant site toujours non sécurisé et inacessible sur certains navigateurs Mon nom de domaine est : [bap.a3a-architecture.fr/](http://bap.a3a-architecture.fr/) J’ai exécuté cette commande : sudo certbot renew --cert-name [bap.a3a-architecture.fr](http://bap.a3a-architecture.fr) Elle a produit cette sortie : The following certificates are not due for renewal yet: /etc/letsencrypt/live/bap.a3a-architecture.fr/fullchain.pem expires on 2025-02-05 (skipped) No renewals were attempted. Mon serveur Web est (inclure la version) : MAMP Pro 5.5.1 Le système d’exploitation sur lequel mon serveur Web s’exécute est (version incluse) : Monterey 12.7.6 Mon hébergeur, le cas échéant, est : Je peux me connecter à un shell root sur ma machine (oui ou non, ou je ne sais pas) : oui J’utilise un panneau de configuration pour gérer mon site (non, ou fournit le nom et la version du panneau de configuration) : non ---
**Author:** ![Mic](https://avatars.discourse-cdn.com/v4/letter/m/e0b2c6/32.png) [@Mic](https://community.letsencrypt.org/u/Mic)\ **Post date:** [November 7, 2024, 2:58pm UTC](https://community.letsencrypt.org/t/https-bap-a3a-architecture-fr/228385/4 "2024-11-07T14:58:02Z")
> [@Osiris](#): > > `certbot certificates` Avec le commande certbot certificates, j'obtiens ceci : admin$ certbot certificates The following error was encountered: [Errno 13] Permission denied: '/var/log/letsencrypt/.certbot.lock' Either run as root, or set --config-dir, --work-dir, and --logs-dir to writeable paths. Je ne sais pas quoi faire avec ça ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [November 7, 2024, 3:02pm UTC](https://community.letsencrypt.org/t/https-bap-a3a-architecture-fr/228385/5 "2024-11-07T15:02:03Z")
> [@Mic](#): > > certbot certificates try ```nohighlight sudo certbot certificates ``` ---
**Author:** ![Mic](https://avatars.discourse-cdn.com/v4/letter/m/e0b2c6/32.png) [@Mic](https://community.letsencrypt.org/u/Mic)\ **Post date:** [November 7, 2024, 3:16pm UTC](https://community.letsencrypt.org/t/https-bap-a3a-architecture-fr/228385/6 "2024-11-07T15:16:10Z")
Thank you Ok now i get this : admin$ sudo certbot certificates Saving debug log to /var/log/letsencrypt/letsencrypt.log * * * Found the following certs: Certificate Name: [bap.a3a-architecture.fr](http://bap.a3a-architecture.fr) Serial Number: 47f37f12731d49a11cce083f9530ffda06d Key Type: ECDSA Domains: [bap.a3a-architecture.fr](http://bap.a3a-architecture.fr) Expiry Date: 2025-02-05 14:11:40+00:00 (VALID: 89 days) Certificate Path: /etc/letsencrypt/live/bap.a3a-architecture.fr/fullchain.pem Private Key Path: /etc/letsencrypt/live/bap.a3a-architecture.fr/privkey.pem it seems to expier on 2025-02-05 however on my browsers the website is not secured and is expired since 10/30/2024 ; Have i missed something ? ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [November 7, 2024, 3:25pm UTC](https://community.letsencrypt.org/t/https-bap-a3a-architecture-fr/228385/7 "2024-11-07T15:25:30Z")
Did you restart Apache after getting the cert? ---
**Author:** ![Mic](https://avatars.discourse-cdn.com/v4/letter/m/e0b2c6/32.png) [@Mic](https://community.letsencrypt.org/u/Mic)\ **Post date:** [November 7, 2024, 4:00pm UTC](https://community.letsencrypt.org/t/https-bap-a3a-architecture-fr/228385/8 "2024-11-07T16:00:48Z")
U're absolutely right it's now renew to 2025-02-05 Thank you so much Great help ---
**Author:** ![Mic](https://avatars.discourse-cdn.com/v4/letter/m/e0b2c6/32.png) [@Mic](https://community.letsencrypt.org/u/Mic)\ **Post date:** [November 7, 2024, 4:03pm UTC](https://community.letsencrypt.org/t/https-bap-a3a-architecture-fr/228385/9 "2024-11-07T16:03:17Z")
How can i set an automatic renewal on that certificate ? ---
**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\ **Post date:** [November 7, 2024, 5:23pm UTC](https://community.letsencrypt.org/t/https-bap-a3a-architecture-fr/228385/10 "2024-11-07T17:23:43Z")
The cert probably is auto-renewing. The problem [to me] seems to be that the web server doesn't auto-restart/reload after the cert has been renewed. ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [November 7, 2024, 6:18pm UTC](https://community.letsencrypt.org/t/https-bap-a3a-architecture-fr/228385/11 "2024-11-07T18:18:32Z")
You can add a `--deploy-hook` with a specific reload command for your webserver, which wil run if the certificate was renewed. You can use `sudo certbot reconfigure --cert-name bap.a3a-architecture.fr --deploy-hook "enter reload command here"` to reconfigure your existing certificate for future renewals. (If your Certbot is new enough.) ---
**Author:** ![Mic](https://avatars.discourse-cdn.com/v4/letter/m/e0b2c6/32.png) [@Mic](https://community.letsencrypt.org/u/Mic)\ **Post date:** [November 7, 2024, 6:58pm UTC](https://community.letsencrypt.org/t/https-bap-a3a-architecture-fr/228385/12 "2024-11-07T18:58:53Z")
Thank you rg305 and Osiris will try that and will let you know. ---
**Author:** ![Mic](https://avatars.discourse-cdn.com/v4/letter/m/e0b2c6/32.png) [@Mic](https://community.letsencrypt.org/u/Mic)\ **Post date:** [November 11, 2024, 10:10am UTC](https://community.letsencrypt.org/t/https-bap-a3a-architecture-fr/228385/13 "2024-11-11T10:10:18Z")
Hello as i'm not really sure about the syntax for this command, am i on the good path with that ? sudo certbot reconfigure --cert-name [bap.a3a-architecture.fr](http://bap.a3a-architecture.fr) --deploy-hook “service apache reload" ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [November 11, 2024, 12:15pm UTC](https://community.letsencrypt.org/t/https-bap-a3a-architecture-fr/228385/14 "2024-11-11T12:15:48Z")
Yes, that should entirely be the correct command. ---
**Author:** ![Mic](https://avatars.discourse-cdn.com/v4/letter/m/e0b2c6/32.png) [@Mic](https://community.letsencrypt.org/u/Mic)\ **Post date:** [December 2, 2024, 9:02am UTC](https://community.letsencrypt.org/t/https-bap-a3a-architecture-fr/228385/15 "2024-12-02T09:02:21Z")
hi everybody ok the latest command is enter now i have a new error message, logs here 🙂 [Thu Nov 28 22:59:19 2024] [error] [client 67.60.128.211] Invalid URI in request POST /cgi-bin/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/bin/sh HTTP/1.1 [Fri Nov 29 00:04:02 2024] [error] [client 60.221.228.127] Invalid URI in request POST /cgi-bin/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/bin/sh HTTP/1.1 [Fri Nov 29 04:44:44 2024] [error] Hostname cloud.a3a.archi provided via SNI and hostname 81.250.146.229 provided via HTTP are different [Fri Nov 29 19:24:20 2024] [error] [client 47.251.31.177] Invalid URI in request POST /cgi-bin/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/bin/sh HTTP/1.1 [Fri Nov 29 22:22:26 2024] [error] [client 79.124.58.138] File does not exist: /Applications/MAMP/htdocs/bap/web/.git [Sat Nov 30 08:01:15 2024] [error] [client 8.222.197.183] Invalid URI in request POST /cgi-bin/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/bin/sh HTTP/1.1 [Sun Dec 01 00:16:53 2024] [error] Hostname office.a3a.archi provided via SNI and hostname 81.250.146.229 provided via HTTP are different [Sun Dec 01 02:25:00 2024] [error] [client 159.65.89.227] Invalid Content-Length [Sun Dec 01 04:05:28 2024] [error] [client 172.105.246.139] Invalid Content-Length [Sun Dec 01 04:05:46 2024] [error] [client 172.105.246.139] Invalid URI in request GET default.asp HTTP/1.1 [Sun Dec 01 04:07:56 2024] [error] [client 27.106.121.146] Invalid URI in request POST /cgi-bin/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/bin/sh HTTP/1.1 [Sun Dec 01 07:50:46 2024] [error] [client 8.218.133.9] Invalid URI in request POST /cgi-bin/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/bin/sh HTTP/1.1 [Sun Dec 01 09:52:56 2024] [error] Hostname [bap.a3a-architecture.fr](http://bap.a3a-architecture.fr) provided via SNI and hostname 81.250.146.229 provided via HTTP are different [Sun Dec 01 22:06:31 2024] [error] [client 57.141.0.27] File does not exist: /Applications/MAMP/htdocs/bap/web/.well-known [Mon Dec 02 03:13:35 2024] [error] [client 8.216.86.132] Invalid URI in request POST /cgi-bin/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/bin/sh HTTP/1.1 [Mon Dec 02 05:53:17 2024] [error] [client 144.126.229.46] Invalid URI in request POST /cgi-bin/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/bin/sh HTTP/1.1 [Mon Dec 02 09:50:26 2024] [notice] caught SIGTERM, shutting down Any idea ? Thanks community ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [December 2, 2024, 9:06am UTC](https://community.letsencrypt.org/t/https-bap-a3a-architecture-fr/228385/16 "2024-12-02T09:06:36Z")
Those are just random scripted "attacks" against "known exploits". They show up in the logs of every webserver connected to the internet. In this case it's an attempt to exploit [CVE-2021-41773](https://nvd.nist.gov/vuln/detail/cve-2021-41773). ---
**Author:** ![Mic](https://avatars.discourse-cdn.com/v4/letter/m/e0b2c6/32.png) [@Mic](https://community.letsencrypt.org/u/Mic)\ **Post date:** [December 2, 2024, 9:06am UTC](https://community.letsencrypt.org/t/https-bap-a3a-architecture-fr/228385/17 "2024-12-02T09:06:48Z")
i have this message ![Capture d’écran 2024-12-02 à 10.05.21](https://global.discourse-cdn.com/letsencrypt/original/3X/3/7/3773faa116b34d5bc1377bcb0665493caa56c784.png) Ports 80 and 443 are open on the router ---
**Author:** ![Mic](https://avatars.discourse-cdn.com/v4/letter/m/e0b2c6/32.png) [@Mic](https://community.letsencrypt.org/u/Mic)\ **Post date:** [December 2, 2024, 9:55am UTC](https://community.letsencrypt.org/t/https-bap-a3a-architecture-fr/228385/18 "2024-12-02T09:55:00Z")
i've added an htaccess file here /Applications/MAMP/htdocs/bap/web/ with this command : RewriteEngine On RewriteCond %{REQUEST\_URI} ../ RewriteRule ^ - [F,L] Same error ---
**Author:** ![Mic](https://avatars.discourse-cdn.com/v4/letter/m/e0b2c6/32.png) [@Mic](https://community.letsencrypt.org/u/Mic)\ **Post date:** [December 2, 2024, 11:39am UTC](https://community.letsencrypt.org/t/https-bap-a3a-architecture-fr/228385/19 "2024-12-02T11:39:44Z")
résolu avec IA merci à tous ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [January 1, 2025, 11:40am UTC](https://community.letsencrypt.org/t/https-bap-a3a-architecture-fr/228385/20 "2025-01-01T11:40:21Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.