Letsencrypt SPAM logs

Bonjour,

J'utilise lets encrypt depuis des années et tout se passe bien. Les certificats se renouvellent automatiquement etc...

En revanche, malgré que tout fonctionne parfaitement je reçois beaucoup d'erreurs dans mes logs voici un apercu rien que pour la journée d'aujourd'hui :

2024/03/05 00:21:22 [error] 23620#23620: *2075279 open() "/tmp/well-known/about.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/about.php HTTP/1.0", host: "www.agendbox.com"
2024/03/05 00:21:27 [error] 23620#23620: *2075280 open() "/tmp/well-known/pki-validation/about.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/pki-validation/about.php HTTP/1.0", host: "www.agendbox.com"
2024/03/05 00:21:35 [error] 23619#23619: *2075283 open() "/tmp/well-known/pki-validation/cloud.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/pki-validation/cloud.php HTTP/1.0", host: "www.agendbox.com"
2024/03/05 00:21:36 [error] 23619#23619: *2075284 open() "/tmp/well-known/acme-challenge/cloud.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/acme-challenge/cloud.php HTTP/1.0", host: "www.agendbox.com"
2024/03/05 00:22:04 [error] 23619#23619: *2075289 open() "/tmp/well-known/acme-challenge/cloud.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/acme-challenge/cloud.php HTTP/1.0", host: "www.agendbox.com"
2024/03/05 00:22:09 [error] 23619#23619: *2075290 open() "/tmp/well-known/pki-validation/xmrlpc.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/pki-validation/xmrlpc.php?p= HTTP/1.0", host: "www.agendbox.com"
2024/03/05 00:22:09 [error] 23619#23619: *2075291 open() "/tmp/well-known/acme-challenge/xmrlpc.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/acme-challenge/xmrlpc.php?p= HTTP/1.0", host: "www.agendbox.com"
2024/03/05 00:22:20 [error] 23619#23619: *2075293 open() "/tmp/well-known/about.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/about.php HTTP/1.0", host: "www.agendbox.com"
2024/03/05 00:22:25 [error] 23619#23619: *2075295 open() "/tmp/well-known/pki-validation/about.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/pki-validation/about.php HTTP/1.0", host: "www.agendbox.com"
2024/03/05 00:22:33 [error] 23619#23619: *2075296 open() "/tmp/well-known/pki-validation/cloud.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/pki-validation/cloud.php HTTP/1.0", host: "www.agendbox.com"
2024/03/05 00:22:34 [error] 23619#23619: *2075297 open() "/tmp/well-known/acme-challenge/cloud.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/acme-challenge/cloud.php HTTP/1.0", host: "www.agendbox.com"
2024/03/05 00:23:02 [error] 23620#23620: *2075301 open() "/tmp/well-known/acme-challenge/cloud.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/acme-challenge/cloud.php HTTP/1.0", host: "www.agendbox.com"
2024/03/05 00:23:07 [error] 23620#23620: *2075302 open() "/tmp/well-known/pki-validation/xmrlpc.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/pki-validation/xmrlpc.php?p= HTTP/1.0", host: "www.agendbox.com"
2024/03/05 00:23:07 [error] 23620#23620: *2075303 open() "/tmp/well-known/acme-challenge/xmrlpc.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/acme-challenge/xmrlpc.php?p= HTTP/1.0", host: "www.agendbox.com"
2024/03/05 00:49:43 [error] 23620#23620: *2075508 open() "/tmp/well-known/acme-challenge/L6--ZTU0MT75NTCUG_Q1OBA28KGFEZJX" failed (2: No such file or directory), client: 172.68.77.18, server: glass-wash.fr, request: "GET /.well-known/acme-challenge/L6--ZTU0MT75NTCUG_Q1OBA28KGFEZJX HTTP/1.1", host: "cpanel.glass-wash.fr"
2024/03/05 00:49:43 [error] 23620#23620: *2075509 open() "/tmp/well-known/acme-challenge/US2ZILRK2JUXDMB7Y9ZD2E3EPPRMUSXL" failed (2: No such file or directory), client: 172.68.77.25, server: glass-wash.fr, request: "GET /.well-known/acme-challenge/US2ZILRK2JUXDMB7Y9ZD2E3EPPRMUSXL HTTP/1.1", host: "webdisk.glass-wash.fr"
2024/03/05 00:49:43 [error] 23620#23620: *2075510 open() "/tmp/well-known/acme-challenge/J66AHUTTG89RRYRURBQ_KRYI7NXIZK5Z" failed (2: No such file or directory), client: 172.68.77.7, server: glass-wash.fr, request: "GET /.well-known/acme-challenge/J66AHUTTG89RRYRURBQ_KRYI7NXIZK5Z HTTP/1.1", host: "cpcontacts.glass-wash.fr"
2024/03/05 00:49:44 [error] 23620#23620: *2075511 open() "/tmp/well-known/acme-challenge/N9ARFUSWL7X5V9NU1PUAL6X3SFOY5EF-" failed (2: No such file or directory), client: 172.68.77.19, server: glass-wash.fr, request: "GET /.well-known/acme-challenge/N9ARFUSWL7X5V9NU1PUAL6X3SFOY5EF- HTTP/1.1", host: "cpcalendars.glass-wash.fr"
2024/03/05 01:32:08 [error] 23619#23619: *2075852 "/tmp/well-known/index.html" is not found (2: No such file or directory), client: 108.162.210.201, server: myappliz.com, request: "GET /.well-known/ HTTP/1.1", host: "myappliz.com", referrer: "binance.com"
2024/03/05 02:07:20 [error] 23620#23620: *2076130 open() "/tmp/well-known/amaxx.php" failed (2: No such file or directory), client: 45.131.195.221, server: remplacement-parebrise-limoges.fr, request: "GET /_well-known/amaxx.php HTTP/1.1", host: "remplacement-parebrise-limoges.fr"
2024/03/05 02:07:33 [error] 23620#23620: *2076130 open() "/tmp/well-known/wso112233.php" failed (2: No such file or directory), client: 45.131.195.221, server: remplacement-parebrise-limoges.fr, request: "GET /.well-known/wso112233.php HTTP/1.1", host: "remplacement-parebrise-limoges.fr"
2024/03/05 02:07:39 [error] 23620#23620: *2076130 open() "/tmp/well-known/pki-validation/about.php" failed (2: No such file or directory), client: 45.131.195.221, server: remplacement-parebrise-limoges.fr, request: "GET /.well-known/pki-validation/about.php HTTP/1.1", host: "remplacement-parebrise-limoges.fr"
2024/03/05 02:07:53 [error] 23620#23620: *2076130 open() "/tmp/well-known/wso112233.php" failed (2: No such file or directory), client: 45.131.195.221, server: remplacement-parebrise-limoges.fr, request: "GET /.well-known/wso112233.php HTTP/1.1", host: "remplacement-parebrise-limoges.fr"
2024/03/05 02:07:56 [error] 23620#23620: *2076130 open() "/tmp/well-known/pki-validation/about.php" failed (2: No such file or directory), client: 45.131.195.221, server: remplacement-parebrise-limoges.fr, request: "GET /.well-known/pki-validation/about.php HTTP/1.1", host: "remplacement-parebrise-limoges.fr"
2024/03/05 03:49:43 [error] 24529#24529: *2076954 open() "/tmp/well-known/acme-challenge/I_2HS6-RXO0J4ZOABAERC3FC7NYULPSC" failed (2: No such file or directory), client: 172.68.77.3, server: glass-wash.fr, request: "GET /.well-known/acme-challenge/I_2HS6-RXO0J4ZOABAERC3FC7NYULPSC HTTP/1.1", host: "cpanel.glass-wash.fr"
2024/03/05 03:49:43 [error] 24529#24529: *2076955 open() "/tmp/well-known/acme-challenge/RX-NR9X4A2RFH13VPOTO7JHP4QRUCJHK" failed (2: No such file or directory), client: 172.68.77.8, server: glass-wash.fr, request: "GET /.well-known/acme-challenge/RX-NR9X4A2RFH13VPOTO7JHP4QRUCJHK HTTP/1.1", host: "webdisk.glass-wash.fr"
2024/03/05 03:49:44 [error] 24529#24529: *2076956 open() "/tmp/well-known/acme-challenge/33E8WA62OQ8HZAP_DXEI1N7CGY96464L" failed (2: No such file or directory), client: 172.68.77.6, server: glass-wash.fr, request: "GET /.well-known/acme-challenge/33E8WA62OQ8HZAP_DXEI1N7CGY96464L HTTP/1.1", host: "cpcontacts.glass-wash.fr"
2024/03/05 03:49:44 [error] 24529#24529: *2076957 open() "/tmp/well-known/acme-challenge/90AU7NG0DA-STBH_W6UEKIKYY3L33MK0" failed (2: No such file or directory), client: 172.68.77.17, server: glass-wash.fr, request: "GET /.well-known/acme-challenge/90AU7NG0DA-STBH_W6UEKIKYY3L33MK0 HTTP/1.1", host: "cpcalendars.glass-wash.fr"
2024/03/05 05:15:21 [error] 24529#24529: *2077547 open() "/tmp/well-known/about.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/about.php HTTP/1.0", host: "agendbox.com"
2024/03/05 05:15:25 [error] 24528#24528: *2077549 open() "/tmp/well-known/pki-validation/about.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/pki-validation/about.php HTTP/1.0", host: "agendbox.com"
2024/03/05 05:15:31 [error] 24528#24528: *2077550 open() "/tmp/well-known/pki-validation/cloud.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/pki-validation/cloud.php HTTP/1.0", host: "agendbox.com"
2024/03/05 05:15:31 [error] 24528#24528: *2077551 open() "/tmp/well-known/acme-challenge/cloud.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/acme-challenge/cloud.php HTTP/1.0", host: "agendbox.com"
2024/03/05 05:15:52 [error] 24528#24528: *2077556 open() "/tmp/well-known/acme-challenge/cloud.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/acme-challenge/cloud.php HTTP/1.0", host: "agendbox.com"
2024/03/05 05:15:55 [error] 24528#24528: *2077558 open() "/tmp/well-known/pki-validation/xmrlpc.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/pki-validation/xmrlpc.php?p= HTTP/1.0", host: "agendbox.com"
2024/03/05 05:15:56 [error] 24528#24528: *2077559 open() "/tmp/well-known/acme-challenge/xmrlpc.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/acme-challenge/xmrlpc.php?p= HTTP/1.0", host: "agendbox.com"
2024/03/05 05:16:04 [error] 24528#24528: *2077566 open() "/tmp/well-known/about.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/about.php HTTP/1.0", host: "agendbox.com"
2024/03/05 05:16:08 [error] 24528#24528: *2077574 open() "/tmp/well-known/pki-validation/about.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/pki-validation/about.php HTTP/1.0", host: "agendbox.com"
2024/03/05 05:16:14 [error] 24528#24528: *2077582 open() "/tmp/well-known/pki-validation/cloud.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/pki-validation/cloud.php HTTP/1.0", host: "agendbox.com"
2024/03/05 05:16:14 [error] 24528#24528: *2077583 open() "/tmp/well-known/acme-challenge/cloud.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/acme-challenge/cloud.php HTTP/1.0", host: "agendbox.com"
2024/03/05 05:16:36 [error] 24529#24529: *2077597 open() "/tmp/well-known/acme-challenge/cloud.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/acme-challenge/cloud.php HTTP/1.0", host: "agendbox.com"
2024/03/05 05:16:39 [error] 24529#24529: *2077598 open() "/tmp/well-known/pki-validation/xmrlpc.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/pki-validation/xmrlpc.php?p= HTTP/1.0", host: "agendbox.com"
2024/03/05 05:16:40 [error] 24529#24529: *2077599 open() "/tmp/well-known/acme-challenge/xmrlpc.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/acme-challenge/xmrlpc.php?p= HTTP/1.0", host: "agendbox.com"
2024/03/05 05:29:50 [error] 24528#24528: *2077707 open() "/tmp/well-known/acme-challenge/2cca1f36551dffb21d64b7c277724b19.txt" failed (2: No such file or directory), client: 172.69.222.38, server: faciliglass.fr, request: "GET /.well-known/acme-challenge/2cca1f36551dffb21d64b7c277724b19.txt HTTP/1.1", host: "faciliglass.fr"
2024/03/05 05:29:50 [error] 24528#24528: *2077708 open() "/tmp/well-known/acme-challenge/2cca1f36551dffb21d64b7c277724b19.txt" failed (2: No such file or directory), client: 172.71.134.215, server: faciliglass.fr, request: "GET /.well-known/acme-challenge/2cca1f36551dffb21d64b7c277724b19.txt HTTP/1.1", host: "www.faciliglass.fr"
2024/03/05 05:29:50 [error] 24528#24528: *2077709 open() "/tmp/well-known/acme-challenge/2cca1f36551dffb21d64b7c277724b19.txt" failed (2: No such file or directory), client: 172.69.222.32, server: faciliglass.fr, request: "GET /.well-known/acme-challenge/2cca1f36551dffb21d64b7c277724b19.txt HTTP/1.1", host: "faciliglass.fr"
2024/03/05 05:29:50 [error] 24528#24528: *2077710 open() "/tmp/well-known/acme-challenge/2cca1f36551dffb21d64b7c277724b19.txt" failed (2: No such file or directory), client: 172.69.222.21, server: faciliglass.fr, request: "GET /.well-known/acme-challenge/2cca1f36551dffb21d64b7c277724b19.txt HTTP/1.1", host: "www.faciliglass.fr"
2024/03/05 06:39:26 [error] 24529#24529: *2078322 open() "/tmp/well-known/acme-challenge/f11a21402056a66f204361d38ff81152.txt" failed (2: No such file or directory), client: 31.207.33.203, server: glass-wash-limoges.fr, request: "GET /.well-known/acme-challenge/f11a21402056a66f204361d38ff81152.txt HTTP/1.0", host: "glass-wash-limoges.fr"
2024/03/05 06:39:26 [error] 24529#24529: *2078323 open() "/tmp/well-known/acme-challenge/f11a21402056a66f204361d38ff81152.txt" failed (2: No such file or directory), client: 31.207.33.203, server: glass-wash-limoges.fr, request: "GET /.well-known/acme-challenge/f11a21402056a66f204361d38ff81152.txt HTTP/1.0", host: "www.glass-wash-limoges.fr"
2024/03/05 06:49:04 [error] 24529#24529: *2078395 open() "/tmp/well-known/acme-challenge/X99FZ-Y_P24K0JMK1PJ-C5J91OBFKYUI" failed (2: No such file or directory), client: 172.68.77.2, server: glass-wash.fr, request: "GET /.well-known/acme-challenge/X99FZ-Y_P24K0JMK1PJ-C5J91OBFKYUI HTTP/1.1", host: "cpanel.glass-wash.fr"
2024/03/05 06:49:05 [error] 24529#24529: *2078396 open() "/tmp/well-known/acme-challenge/W_4CV3-UZ9O1TOHKO5AVBPRN04M9QRND" failed (2: No such file or directory), client: 172.68.77.25, server: glass-wash.fr, request: "GET /.well-known/acme-challenge/W_4CV3-UZ9O1TOHKO5AVBPRN04M9QRND HTTP/1.1", host: "webdisk.glass-wash.fr"
2024/03/05 06:49:05 [error] 24529#24529: *2078397 open() "/tmp/well-known/acme-challenge/WN5CQDVFFN1K479UWMPTYC7CF81MWKM7" failed (2: No such file or directory), client: 172.68.77.15, server: glass-wash.fr, request: "GET /.well-known/acme-challenge/WN5CQDVFFN1K479UWMPTYC7CF81MWKM7 HTTP/1.1", host: "cpcontacts.glass-wash.fr"
2024/03/05 06:49:05 [error] 24529#24529: *2078398 open() "/tmp/well-known/acme-challenge/USRUXLQWQOF9ZCJN1AXNECFCG6OEVAKQ" failed (2: No such file or directory), client: 172.68.77.16, server: glass-wash.fr, request: "GET /.well-known/acme-challenge/USRUXLQWQOF9ZCJN1AXNECFCG6OEVAKQ HTTP/1.1", host: "cpcalendars.glass-wash.fr"
2024/03/05 08:04:54 [error] 24528#24528: *2079043 open() "/tmp/well-known/about.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/about.php HTTP/1.0", host: "agendbox.com"
2024/03/05 08:04:57 [error] 24528#24528: *2079044 open() "/tmp/well-known/pki-validation/about.php" failed (2: No such file or directory), client: 31.207.33.203, server: agendbox.com, request: "GET /.well-known/pki-validation/about.php HTTP/1.0", host: "agendbox.com"

Pensez-vous qu'il s'agit d'une erreur de configuration ou de SPAM ? Comment y mettre fin ?

Logs letsencrypt de ce jour :
2024-03-03 08:49:16,724:DEBUG:certbot.main:certbot version: 0.31.0
2024-03-03 08:49:16,724:DEBUG:certbot.main:Arguments: ['-q']
2024-03-03 08:49:16,725:DEBUG:certbot.main:Discovered plugins: PluginsRegistry(PluginEntryPoint#manual,PluginEntryPoint#nginx,PluginEntryPoint#null,PluginEntryPoint#standalone,PluginEntryPoint#webroot)
2024-03-03 08:49:16,734:DEBUG:certbot.log:Root logging level set at 30
2024-03-03 08:49:16,735:INFO:certbot.log:Saving debug log to /var/log/letsencrypt/letsencrypt.log
2024-03-03 08:49:16,744:DEBUG:certbot.plugins.selection:Requested authenticator <certbot.cli._Default object at 0x7fae8e4d06a0> and installer <certbot.cli._Default object at 0x7fae8e4d06a0>
2024-03-03 08:49:16,744:DEBUG:certbot.cli:Var deploy_hook=unison for_letsencrypt && unison for_letsencrypt_sym && systemctl reload nginx (set by user).
2024-03-03 08:49:16,744:DEBUG:certbot.cli:Var renew_hook={'deploy_hook'} (set by user).
2024-03-03 08:49:16,769:INFO:certbot.renewal:Cert not yet due for renewal
2024-03-03 08:49:16,771:DEBUG:certbot.plugins.selection:Requested authenticator nginx and installer nginx
2024-03-03 08:49:16,771:DEBUG:certbot.plugins.selection:Selecting plugin: * nginx
Description: Nginx Web Server plugin
Interfaces: IAuthenticator, IInstaller, IPlugin
Entry point: nginx = certbot_nginx.configurator:NginxConfigurator
Initialized: <certbot_nginx.configurator.NginxConfigurator object at 0x7fae8f81bfd0>
2024-03-03 08:49:16,772:DEBUG:certbot.renewal:no renewal failures
2024-03-03 14:11:09,653:DEBUG:certbot.main:certbot version: 0.31.0
2024-03-03 14:11:09,654:DEBUG:certbot.main:Arguments: ['-q']
2024-03-03 14:11:09,654:DEBUG:certbot.main:Discovered plugins: PluginsRegistry(PluginEntryPoint#manual,PluginEntryPoint#nginx,PluginEntryPoint#null,PluginEntryPoint#standalone,PluginEntryPoint#webroot)
2024-03-03 14:11:09,663:DEBUG:certbot.log:Root logging level set at 30
2024-03-03 14:11:09,663:INFO:certbot.log:Saving debug log to /var/log/letsencrypt/letsencrypt.log
2024-03-03 14:11:09,672:DEBUG:certbot.plugins.selection:Requested authenticator <certbot.cli._Default object at 0x7f28f2cc5668> and installer <certbot.cli._Default object at 0x7f28f2cc5668>
2024-03-03 14:11:09,672:DEBUG:certbot.cli:Var deploy_hook=unison for_letsencrypt && unison for_letsencrypt_sym && systemctl reload nginx (set by user).
2024-03-03 14:11:09,672:DEBUG:certbot.cli:Var renew_hook={'deploy_hook'} (set by user).
2024-03-03 14:11:09,696:INFO:certbot.renewal:Cert not yet due for renewal
2024-03-03 14:11:09,697:DEBUG:certbot.plugins.selection:Requested authenticator nginx and installer nginx
2024-03-03 14:11:09,698:DEBUG:certbot.plugins.selection:Selecting plugin: * nginx
Description: Nginx Web Server plugin
Interfaces: IAuthenticator, IInstaller, IPlugin
Entry point: nginx = certbot_nginx.configurator:NginxConfigurator
Initialized: <certbot_nginx.configurator.NginxConfigurator object at 0x7f28f4010fd0>
2024-03-03 14:11:09,698:DEBUG:certbot.renewal:no renewal failures
2024-03-04 06:48:18,591:DEBUG:certbot.main:certbot version: 0.31.0
2024-03-04 06:48:18,592:DEBUG:certbot.main:Arguments: ['-q']
2024-03-04 06:48:18,592:DEBUG:certbot.main:Discovered plugins: PluginsRegistry(PluginEntryPoint#manual,PluginEntryPoint#nginx,PluginEntryPoint#null,PluginEntryPoint#standalone,PluginEntryPoint#webroot)
2024-03-04 06:48:18,601:DEBUG:certbot.log:Root logging level set at 30
2024-03-04 06:48:18,601:INFO:certbot.log:Saving debug log to /var/log/letsencrypt/letsencrypt.log
2024-03-04 06:48:18,609:DEBUG:certbot.plugins.selection:Requested authenticator <certbot.cli._Default object at 0x7f55aba186a0> and installer <certbot.cli._Default object at 0x7f55aba186a0>
2024-03-04 06:48:18,609:DEBUG:certbot.cli:Var deploy_hook=unison for_letsencrypt && unison for_letsencrypt_sym && systemctl reload nginx (set by user).
2024-03-04 06:48:18,609:DEBUG:certbot.cli:Var renew_hook={'deploy_hook'} (set by user).
2024-03-04 06:48:18,633:INFO:certbot.renewal:Cert not yet due for renewal
2024-03-04 06:48:18,634:DEBUG:certbot.plugins.selection:Requested authenticator nginx and installer nginx
2024-03-04 06:48:18,634:DEBUG:certbot.plugins.selection:Selecting plugin: * nginx
Description: Nginx Web Server plugin
Interfaces: IAuthenticator, IInstaller, IPlugin
Entry point: nginx = certbot_nginx.configurator:NginxConfigurator
Initialized: <certbot_nginx.configurator.NginxConfigurator object at 0x7f55acd63ba8>
2024-03-04 06:48:18,635:DEBUG:certbot.renewal:no renewal failures
2024-03-04 14:06:39,483:DEBUG:certbot.main:certbot version: 0.31.0
2024-03-04 14:06:39,483:DEBUG:certbot.main:Arguments: ['-q']
2024-03-04 14:06:39,484:DEBUG:certbot.main:Discovered plugins: PluginsRegistry(PluginEntryPoint#manual,PluginEntryPoint#nginx,PluginEntryPoint#null,PluginEntryPoint#standalone,PluginEntryPoint#webroot)
2024-03-04 14:06:39,493:DEBUG:certbot.log:Root logging level set at 30
2024-03-04 14:06:39,493:INFO:certbot.log:Saving debug log to /var/log/letsencrypt/letsencrypt.log
2024-03-04 14:06:39,502:DEBUG:certbot.plugins.selection:Requested authenticator <certbot.cli._Default object at 0x7f4ec30d27b8> and installer <certbot.cli._Default object at 0x7f4ec30d27b8>
2024-03-04 14:06:39,502:DEBUG:certbot.cli:Var deploy_hook=unison for_letsencrypt && unison for_letsencrypt_sym && systemctl reload nginx (set by user).
2024-03-04 14:06:39,502:DEBUG:certbot.cli:Var renew_hook={'deploy_hook'} (set by user).
2024-03-04 14:06:39,528:INFO:certbot.renewal:Cert not yet due for renewal
2024-03-04 14:06:39,529:DEBUG:certbot.plugins.selection:Requested authenticator nginx and installer nginx
2024-03-04 14:06:39,530:DEBUG:certbot.plugins.selection:Selecting plugin: * nginx
Description: Nginx Web Server plugin
Interfaces: IAuthenticator, IInstaller, IPlugin
Entry point: nginx = certbot_nginx.configurator:NginxConfigurator
Initialized: <certbot_nginx.configurator.NginxConfigurator object at 0x7f4ec441e898>
2024-03-04 14:06:39,530:DEBUG:certbot.renewal:no renewal failures
2024-03-05 05:15:35,635:DEBUG:certbot.main:certbot version: 0.31.0
2024-03-05 05:15:35,636:DEBUG:certbot.main:Arguments: ['-q']
2024-03-05 05:15:35,636:DEBUG:certbot.main:Discovered plugins: PluginsRegistry(PluginEntryPoint#manual,PluginEntryPoint#nginx,PluginEntryPoint#null,PluginEntryPoint#standalone,PluginEntryPoint#webroot)
2024-03-05 05:15:35,645:DEBUG:certbot.log:Root logging level set at 30
2024-03-05 05:15:35,646:INFO:certbot.log:Saving debug log to /var/log/letsencrypt/letsencrypt.log
2024-03-05 05:15:35,655:DEBUG:certbot.plugins.selection:Requested authenticator <certbot.cli._Default object at 0x7fa685e8e710> and installer <certbot.cli._Default object at 0x7fa685e8e710>
2024-03-05 05:15:35,655:DEBUG:certbot.cli:Var deploy_hook=unison for_letsencrypt && unison for_letsencrypt_sym && systemctl reload nginx (set by user).
2024-03-05 05:15:35,655:DEBUG:certbot.cli:Var renew_hook={'deploy_hook'} (set by user).
2024-03-05 05:15:35,680:INFO:certbot.renewal:Cert not yet due for renewal
2024-03-05 05:15:35,681:DEBUG:certbot.plugins.selection:Requested authenticator nginx and installer nginx
2024-03-05 05:15:35,682:DEBUG:certbot.plugins.selection:Selecting plugin: * nginx
Description: Nginx Web Server plugin
Interfaces: IAuthenticator, IInstaller, IPlugin
Entry point: nginx = certbot_nginx.configurator:NginxConfigurator
Initialized: <certbot_nginx.configurator.NginxConfigurator object at 0x7fa685fdcc88>
2024-03-05 05:15:35,682:DEBUG:certbot.renewal:no renewal failures

Merci d'avance pour votre aide

Mon Français, c'est très mal. Je m'excuse d'avance. j'ai dû trop utiliser un dictionnaire. ça fait trop longtemps que je n'ai pas étudié le Français.

La plupart des journaux (logs?) que vous citez sont des scripts testant les vulnérabilités de votre machine. Il est possible que tous proviennent de hackers.

letencrypt pourrait demander-

/.well-known/acme-challenge/90AU7NG0DA-STBH_W6UEKIKYY3L33MK0 HTTP/1.1"

mais je ne demanderai jamais-

/tmp/well-known/pki-validation/about.php
/tmp/well-known/amaxx.php
/tmp/well-known/pki-validation/xmrlpc.php

Vous pourrez peut-être utiliser fail2ban pour bloquer automatiquement ces mauvais ips.

3 Likes

Merci pour votre aide !

C'est bien ce que je me suis dis aussi. D'accord pour :
/tmp/well-known/pki-validation/about.php
/tmp/well-known/amaxx.php
/tmp/well-known/pki-validation/xmrlpc.php

Mais ça ne représente que très peu de requêtes, comment faire pour toutes les autres ? Pour savoir si elles sont loyales ou non ?

Les seules URL que LetsEncrypt tentera de visiter ressembleront à :man_shrugging:

  • /.well-known/acme-challenge/X99FZ-Y_P24K0JMK1PJ-C5J91OBFKYUI

Apres le /.well-known/acme-challenge/ il y aura un chaîne de caractères. RFC 8555 - Automatic Certificate Management Environment (ACME)

A client fulfills this challenge by constructing a key authorization
from the "token" value provided in the challenge and the client's
account key. The client then provisions the key authorization as a
resource on the HTTP server for the domain in question.

The path at which the resource is provisioned is comprised of the
fixed prefix "/.well-known/acme-challenge/", followed by the "token"
value in the challenge. The value of the resource MUST be the ASCII
representation of the key authorization.

GET /.well-known/acme-challenge/LoqXcYV8...jxAjEuX0
Host: example.org
...
...
...

  1. Construct a URL by populating the URL template [RFC6570] "http://{domain}/.well-known/acme-challenge/{token}", where: * the domain field is set to the domain name being verified; and * the token field is set to the token in the challenge.

Letsencrypt ne demandera jamais un fichier "normale" (avec une extension de fichier, mot ordinaire, etc). la chaîne de caractères aura l'air aléatoire et la "output"/sortir" d'une fonction informatique.

3 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.